-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmqD8jcACgkQu9uZGunH
yULo7g//bXqsr0rVWtzCsgKXY7euCV4xN6es48ig//48FDyPnpFekxkr9d76ZDsT
9LOAGHiMtgRhvkF4QjXVW/ZDSE/BiZT16flp9Nep/yTlAQNEITgd8gGCZLaRnz9X
ygb5IqBmu3p4qyV5L1z8Gx4LsIZLjunrDaN9NDC6n103blfqjctxGHowZaWUFfcM
o2hf1GYmnUyObUWYhkKvXzZfZIuto0wdOYOZ7S51/AgHEDO/IA8/gxk2RFW7kJep
HMCmCNlOZdb5dgHWFmUN5tvx79rmeeJtprhiD5s1MbHrnTUO8v42TC57trUXsqVJ
zBRIGqzbirbGymM0tRmTgMpHSPSM5NHrH2mCBRxB15LJD1dwPfSe5/D1uX26U9mh
qrVqWqMmOnEhaAsIunFzEFAUzW3rFrTVwl6JnAsr3D+zdhH8TI6ol0ZRQiaavP+B
m3vAeaxe5NLYgwGZCTCjpdrxQ8hKvC0Ot31yCQtcFYr3D9t8pd8f766mUzMaR8uc
QgKgWiSAeEsRWHf0P7W2UI2a9y3redNHGQubvLB/Dhjy4kh63Nb4lWiKKdjDgLEX
k1SUGMnaGTuTaE4hGfbuZctUL9BS702NBJ1/ABI5bXM30EbQnbd3y9J4dY4lvR6p
/3pl69Q1Jr7zb2EgfOw4oVz/ZbzEVAou5FutXLGCjDPpF4RexcY=
=yvs/
-----END PGP SIGNATURE-----