-----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/jalu9uZGunHyUIFAmrwKrQACgkQu9uZGunH
yUI/aw/8DcvTZxIyq/cZlfKInhYn/AzNiqAX/8I/ho8wHmvcAoSXpaHGCWtk5wMI
8KqrPr3bPs29zQy2JDKOzLJYNwkdc6wScIDR9mtrD5FxQ1neBWOo+dVupmjw0H/9
UY6we6/PX8BmtsfPeDmIoecyFBS0CG1hEhhxQjF2j78/RsrFzN37StQboSyOJe1y
VAV5uQ5f1f9c4MvXB7ZCaFNRr7s+yb5YvEiHo8ZEhxAmsNCYZ9m/cCXySkLwRSjw
kJZaRckzXDoi7j45mLc9qFHYRAxk4KQ4As3GNJdTF+YmDbn57BEAht+NRq0bpRWb
mAoCG5TGRxwjD7fCLommB0Gv8sMQ74ohakcVoHwix4bcyLM3glykyl1NRpcKBsll
fWcO3GV1/uOi/myanFYv/AyuAc2ChbptymmYbhvj3FsVlmpOJ/egrLKeeOYRzFtA
4ejY01pS4Zj+p7go3Ar8Ng2UAv+9oBKQWQa1tl8w6u8oQHRFgqS696nh25a87UV8
ZTb7aKZhjX8WPAl4XdOYYTvD3LCHdEvmn3SaOymEshnm9pzW1ezNi6fN80G86a+n
Osd3+1gYW1JzecRXTORKL8sZmeewtMHlQWpHQJ7quU0q7OOJH3m/i7tcjOR6JS2D
fIuW/JIlky4l2Z2umtrAVRGLvR3BLr3wcrpwESYA1T3y/352hiI=
=VY4k
-----END PGP SIGNATURE-----