-----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/jalu9uZGunHyUIFAmreDg8ACgkQu9uZGunH
yUJLdw/9HoMcGfJMe+4WoF4KbOPs/IqkQwbWhtmHVd9hVxSRiUV8ISDk3ecPsrLW
qIv2JIrF736m/pCmd6Ap2RarGIrG7dxULSCWlY951UQh0hbcNHOU+FQnRWWKjrwV
MrQYiWVQWZOYjJIEeCdY0ETGtCByiay8WKajCWFcWIqRgLvSWCcGGPWSz3/Kml92
FrS3J4EuBeGKXqfccINm8u+dMKQrb3CxPhXx/ALXwK8Zr2IO/q5hnC/cr0PbZOKE
CqIY6UxKVVRaROyo5ecrDqBpC3fXj8ODj0dNSY/k6OepuEItL9O6xfYEP2QGr0r3
ACVchzTvLQuuYlB6oPAJw9J+HVcvbnDIH2EzVcheSvDArmK2r686pjNmVN3oGTWB
iliCalVHg7Dtok4HxwezU4Z5tuAszbk9wRNbsFcVgNb6NWv8F1FQ16CgigLOgpo4
M+chlFxAkzh8gmEbytQvVFHkuD/ZUVng+CRDHRABXLQCbcNFm4WUjXdPcyI2Em89
bKy0HgsIlDmaiHdSVKG+2573famcvz5OnRCwm0Qys8yfsIZD/9msPVIKahGk/AV4
n2SRxa2BNIhZF+uh+6rRQHIb+uwnb7qDAY5q7jwytS17gZweukMuW7Iyt0GB/78D
myBxqZYL2nOWknCzJsXNQbH1rvupexzyhLN71f42kkBMxLOwl88=
=/Qk2
-----END PGP SIGNATURE-----