-----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/jalu9uZGunHyUIFAmpexyMACgkQu9uZGunH
yULtzxAAtGSwbL6/ONv5vCD2uQUIADyGprtTFXBltgAjNfrjm3Krsld5z/d/uB6S
yztzm+DzzYWGK6euB36r9V9fGqPEwyUnscD9vOqYf5VjeFj78gCrfi3dP3jAmTNq
qViByKK0W4EWQbb8ZrYXb33hz1vkSd1rLo0OYCJc8rE0C9jRz3CPyVK/sH4NmRE9
qgQqJO8iZx71NtdlOlZEVpeuX5kD+IrUGN7f7LWU5Bgq5K1nbNs2FFnJEfma+0Ge
F0ZQ42FsUUUN9iSRmwwV/GqQxCggbYj9V6MdZm1ZnPWJvjt/K5nYG4Ympfz20lsD
FR6sjmKPeHy74wpR0mJSby5D7tLtkVdbigUvHIMHFP95So9DRBXwd/nbwzEC6iBH
EKI6G5wmmPVJuIXMSNkD1zlqTPni0kHQ7S2sgFBYEjYPmVM1ZQ243+2DYaLbB4dw
OhjjXRFJOexq5HPz1RDThiTCvI31KZn1IFtgJmYFkP6rvnQo8sPqQjxmOyna7REy
+cdvt9U9OXVuCMWEH9Rsw+7BQSsQuY9ROGNGCm7ijeg8J++B2OW2nmqBcaxTrLGP
6a4LlIOlyUfgJ7NaaAMYIYHQL5iUUR9QmJfh58UmcMbzahvGPK8iCyOPIA41kTMQ
PQUql9ZbZQywz8XKwxnzM3XAugQ49/qw3Ga02u2zNZDlAVFadVs=
=TjUj
-----END PGP SIGNATURE-----