-----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/jalu9uZGunHyUIFAmr6EBEACgkQu9uZGunH
yUKvtg//f2i+0sG9aDWIlmS0j75S3k+AYdyXRMidFKPjIb4nXeE+jeDviSTyEuWd
iEv04bevGFQ+pVHOs5jYd9y7/YI1E2B8DSOwMLrkO8nxHPrZvNvZwUtxfShgCy1u
vXMpCa2NNyOvY2S+wK4Cn/lHYRGD4aRFvxrQXeIuCi71hk7FgydudYg0RI+uyDp/
wk7tBORU1yE4kk5rsSfPu91VzSjJifGi4rSNWl+HKJxs4BiT215/q7qhDQGnesJU
mG/96d/Kg480+NQ8UT/rdWPSXXpR1MHSB8MmfLeDJXB/I333NXF1Qq3X7UD2qGl/
af+w5BIYqdzAu77wdKU2kl4Pq49Yj7kYtyOksVfp8KZKr3naCccQC3llBGn19fm2
VKERdqDIFikbdT7MbFxho5R8jBePiKXSDmSDjyA2047Kl5aYRQWyA8k4mB+UClnQ
rtEDq3B7m1HIUpTihzs/ADH7KfHD+oy4Nu9/qsJxCQa2d8j4HpQKh+6zAFeXRh/b
vL2BOa2X6RxR2IqDWFjxspwqhSlHNyvOFeYCNW2J1oASyReO1JQhEDMMLMcaJV6X
z0aeI0mZhCmR0dWG5357SP05f6fHnounTxDsHuG5BdZrg0jcW82SEy5K0dKxw/vr
uJeBKiPXTdjvFaOljnpu+7raN7hKtwZxl5/UmUWWsRLtg2h1knY=
=KUPW
-----END PGP SIGNATURE-----