-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

Use https://www.quickhash-gui.org/ to verify file integrity hashes in Windows
or you can use the built-in certutil command as described on https://cryptostorm.is/windows

If you're concerned about us using weak algorithms here like md5 and sha1, there's no way to collide md5 and sha1 at the same time.
I.e., you could do a collision with just md5, but that would change the sha1, or vice versa.
That's why you should be checking all 4 hashes, or at least the sha256/512 ones. The md5/sha1 sums are more for CRC than security.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmrlLK0ACgkQu9uZGunH
yULX8BAAlbqLR2ZF70BSPjbzrpmnm1AJc/MTHpPkCD0dsD7V+EztgMwsHx+YxxLz
MbtPSSKoWgfkdQPtEEG2A+W188k2eVdNdXoDPSqfMMQ0oxazHPQBYyVDVm8+CNex
uE5+SRCZagsWof/LguMKHA4DrP+gYPCX2ULzgU8QJRf67BAo/XWBV4Oji7YGWt0y
kOsB+36MOdkRELGOQfoZOrJMw+Cl4TC07g768OkgyiLEdoj51AjmkatuZtc/0Ol5
BUXmmDhhK/lTLE1LIqB0P5gcFPkVbPLim57YJTwIPq4GVe1ndVvIWVXrXzJBNjfi
LwM09mOS5nH73MbnCpwsZjx4vXi2/35dDL9Moy/pkYt77TwQv0mtg4xfGT6QWTWY
mBYx5+/2NM4HH6/TUDTgM55KiSVSe/C7c2bfBuPMxWXlf2kdBafBTRgZlqCnGSUp
wjR5GTbeqNdxVDuxb84BUDsJ1rNzqy/TDuD3aMXRTfobqdC5VG4z3Bj00dVVIyoW
U7FEEazFhJAZX9cvB3BZCAUj4fLs1ySE8yp7pk2vWh9FX291Dtpp+iww557CKFym
eiM5hUp1GHhqg2VY7vody/ylUH6uq6KqtVR26w4JSgQtAMDnaWHCIfxvlZGpUxds
iQM/bkOU9LMZ0e3RNaGRFpGJb3SoNtmJ6dTMZT6IEElrt3IL8s8=
=adiO
-----END PGP SIGNATURE-----