-----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/jalu9uZGunHyUIFAmrxuVEACgkQu9uZGunH
yUJBYQ//SU8xFaPh7dnNV7nPaIzmJEB9stWOQyZEtrSYoFlduH1L2hYg3QcJcpAk
t+ugMAhcP++WiaCKNB7cFx769Huicf+ZrPGg7Q6nRPlBmhyL7DFMyTaKnrZDGEzD
Dlulx3u5F5RnHxqshTKXrDM3SFRiIFS9T+jDbygbGhBxnAacf+bgPhynf+DAJxNt
mZGdi7nCfCkIvFqj0VAo9Jf/oaIbUKVvDCyc1sjTXMbKO7IAX48vIqWQlUhmtV6J
LRuEWjHiUlc2Uk7AQSYklCKIXKn1+9M0CJNLRop+hPdlcgYpEbcMMwKnCMc/3k28
KZ5Mwec6TfDTzHvGzntVstIPXZvrTsad5H3YndyXnpCuVK55er6EjT/EDdINV1sw
oc+XISChzMoU5jYW58fpDpQSMBlszKLX+96YHyaok7kh8yDsDI/pL/3ZCDJalOrL
uDCu8YKaxytozS9zi9/oZRp0yYcjybRJ2xkn1F4jpZhvTTgnlEy8S2K+4AZsgwfq
nAGgbT+lGFrljtG5SM6wcB6hVc+e4jzUt2zs0IEQAjncwORhzTFE9Vl8B7nHVmgk
grNkeOVxyHU2vzb/yxpq4mW4I0/3H8SFQrxSVcCir5m7kpTjwyqM8bMI6WgsQOR1
feAjTDmvkNSkYlZgAhVSO7yfiRBB5oPuQtiQEpO1CW6xIBk5e4A=
=ht/u
-----END PGP SIGNATURE-----