-----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/jalu9uZGunHyUIFAmrpROwACgkQu9uZGunH
yUJi1Q/+LOqf/8XEfPV2PzMi9Do/o3p+HNnZmen58HVsV9FWhSpPnbgJLJ4D6uWM
SSZn9kx5e3KEWZQpJrE0YEqLBzbMxUlieKQPrfZQQajWzesxc5xfkoalW6R8XSHl
ZBIyTH7f8ZZjBAJgmNsHFJury4C/KZ+R7oJCF969FdvgvN58Jd3NypxjC9mZJ1Qy
F/zajbSjWpC2/pqvexopzCuUZolECzUgjWznLVDGsZw6HjS/PNzrhmS9E6CaYBUw
ZEcJKdMJl1NGSGoeKMJBbvYHDchfXnBdVpA9MdQmLy0fH/xkbWJqshRkTr1LRGJn
VD0lYFNsdKoOG2wFCWdgq23JQ/7lk0+sXROnwB36Qwf8GocmY1EneGaQqrplMOoN
AwysR6jyHmO9n2Ju2IWLtBtL3GTcbCiKezROxyfOZM/UV/CowFm4JGJ1h6ZDC4nu
HPWowBilxDw3pTfTtysmhyaCP8qSALT0jC7eZIzCV6p8rBIfzWTFDIKcah5MMUuJ
dscK9UjWdyYirYiu2/sDkHRf9oqJiSFhM9TZYoyH24G8daT+4WslgvI/vtXEbigV
zOpVHIn1j4rhVSi8JyOu/K24HcD935WjK2tQPDekOtMaqnVnovKUeBF/c3zx3cb3
DGsInLld+ROBgifIY8BdU47PuOXY1endt5mVyoOpLeZ5I2eov54=
=efWo
-----END PGP SIGNATURE-----