-----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/jalu9uZGunHyUIFAmrg6J0ACgkQu9uZGunH
yUJGGxAAj4YVEiMAbj4mrzAG/68T4J1fEjKPVJ70N6H+k7G6N6qLgfvWdPwcNlpW
F8WrIXoWmdGOCY1yQ57B0bBTHyV89EsutT65d/toLp1g3t2Um+ctk62ZuutKwsAg
w4l43BSPLvTGkaDCDWZxFjEu/LAhCS8sm3LL6tbp5mPU4D2NiIV7Uly7s6fH0AgE
uJ1IJXvdD/r91cIAomiGmeKuYVjPVSrUGNl+a8+pgs9qPUdgMVoQBTkBmzchVs+K
tnBksaV1aW4dkhXyqPIq4gbxQEDX8yWqyBC0wYTvs0w8jjnfPYbASsKbwBYDO0ki
PjSrt63VD/5ObEQo93C8CNqdWPHyYqQ1bFcC9kWslQghx6zHMU0zPKYgkjkYzXPC
P0qYWC37/4SnqpFUoYS8fEflx6ipHc7qjLnpZIOPtAhVFz/rxtOcr0vAdvYJYoJW
s0aSOTblB0TRBX1RZ+lMh1ToLizKDnzN1KsdklFqSBqADlBu+hXzY/h7xR5qXeiH
F284Vqhn7BmzcspmE8jguTYADOgIz2biH+Ggg8ZcQ+C2qZTKp8/SITcwxnFSOrxE
0ENzR8QVsqTJKlKNiKX8GpHTRJIshnhefo9yaH/AxLfUO8qNO8Q9uUmY9YWE3uAR
YEP66ZvPjGtBR+h0qGJ4h86JIVIw85M7LNdnzTcU5e9xeNb8duo=
=rptS
-----END PGP SIGNATURE-----