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

md5:
3613b1e032d878f162876e61acebe5b7
sha1:
1f3b5c0a51ab4772e8b68ed3ee25386f8fe8dc2e
sha256:
045c8b9fbbbcaaed3486f2819f9a3d9256cd75b603f6579ea1efca16f0ef6383
sha512:
d953f92481a2cbe0371f5666aaa4bff6e725234d7a5b21185fcc9596c33a4add62b09e4ce01b2f4ff87345dc3d7283056e3114ef130c7ea8af6c642ac5fcacfd

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/jalu9uZGunHyUIFAmqXRTYACgkQu9uZGunH
yUK9GA//YlqmGShOUg5HcjE6WWL8KRr3+29G0A8bNuKkQ3U/YxKKClfpISv4hn04
8QS+PSXrN5azh9jIg2cw/VujBOFk6r1REFabn4Ag3wekQ/uKbU1o0ZndyCwV8OH1
oIFQefhLoss7g32uxaZKLOn397+dWErMsmGLHYetETQOi64DHEvB6JVCWEopZHIa
iSBC9AJNnOSY0rHNjuotekXVbPJ6i4AptsAHp3fWZXdTwweQ01zkUy72MP4K4zIk
X5fF1y3LYdPbbkojK2QsDQmlX0bble39RyISuV/bqMfFNvVgj17y6akaGf6OH+ma
IZ2MHbviir4oMHMfe0slPeW3iiTrEQqf9wHC8MstQH9RxnpKPl06Bg8l/HuDP8qz
x2PjDEDpc43BOtiDK5rsLqWaqN0yf1kA9poLsj8AfatYCvAloeveOFs16199OcFp
JUd0vwXelfDVruuRq+YTwOLnPDUbAJQYsaw2f3DfktrlUxE7ZElvOdlCuYnzN1PI
a2nxTwLumXkQHRVkmFK9KfrvV+/FiuWTQDRxGJDiyc/NMbye1kxjO09iiaWuEo6t
RTJ/jo1cCzWpBdGjxswK9dwRSXRsxUBhVVBeArSAEITfaph5SP4H0YnapfEMlkXD
A3uXEuSb5njKuxLvuvD7az5xFKwp1L6/bfvU0852GR1O3WVQZG0=
=aFrm
-----END PGP SIGNATURE-----