-----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/jalu9uZGunHyUIFAmry2Z4ACgkQu9uZGunH
yULkPw//e4xjhbuvRkB7P2njMTyMCTNzRceQCUi8J0Mc129zJJYVdOgciASv1TWL
jjpygM9pAeCo7qorjdFj3b1LlTnednMqdMVMzIH6yPYqVpHhalSzhplFWHTzNIzK
Kfwhw4Oo10S0Gr+p0/dOXzn5fQj4E3SWwwTyE80u/jk3J/o1J2PA02aZYUZxzhAz
/lTqXfhE4/uUXlLcSxXZ7XdX38Mc1quRl9xB8fTd4DF1/0Pjx5UcskjVxpi2yZNi
g9pPJoLBU3B8urDlm64KgLUZKXfD0jbo8z934HLDqG3Z39DDQ8SgmpVlvSqonnGb
mkrpqQhSpzg5geLH6EU0VBLwyWFtPDmdoVFNMJ7jK5ZwHOJwal6s8ka6/7pAyu6/
ZzKWyseCB0RFqi5kQRFx8wGdOtcY5PNoHdzCbvFl9ErXqFn8a2GdmppBHiqUX7uQ
0ltF6ZhuY3V5o2TPexUojn4CWHW6FOymBcGUA7gubKvV9AJUgu9+iD9BKsytJlcm
BMqkyLQ6Y1bc4R/lfXgwnTay7ZotaiUqIFTD+5vWtYOCZuhmEXuCjTSiIVCv9hZC
w7tQVqApjVGTesqEt4x5fXk7VISxVU/TJ1WGLFOglSAi4oDuEmE6bqqxW3GlN+R4
8c3xfejd9z1c0ngdWQrBV4vK9jxDm1yU8TwWonLspoPjM4yGi3s=
=mbT5
-----END PGP SIGNATURE-----