-----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/jalu9uZGunHyUIFAmpanrcACgkQu9uZGunH
yUIj/hAAu2mNWwY/2Ui7lR+TJE8xGLy6rrHazFc+ibR6xcggpGcydp2oW3IcoLpx
IbK9/5lvkkQPGwzqrd03jIZRmttX3tHxTzUiRkE2aT9uub+rjX9dTsR9jyPbz+Jt
xhA5CbP5uJW9d6BXmMtJN1NSrEe7KGgkm7DUTPPgS7GiEqCqidlxEFtaTg7unQr0
JmC0kmjMxPj9/LNlIMw8tiM8/D9tVR6XOUcBMr6rwRh0w70Xq+0gPHzOQoc+lTnN
SOmxk+eACFgpUKlLynEheFP5UpqBIWtn6oWcGapAk8JGGbUAmO49doZTTpFMFFGS
ivq4K52M/NODhk/PY/Nbq0VNKNJHvI9OC0HyRIXCw4S3M++ksoiDnquAhTXIFgCI
ImLXxLDJRhcbz4I+mBMMXh/vQ7H31+h4vF+opOMABz86enwEzDvQTUenZWpGydYb
9Ax25KFXPGMxZ73n6tXIpyz1rU1EtegOnuLbz5+m0ktrph76aZqf7aefk1nqbV5r
IKtvjJ+XxQ9mHdTXtKUIbgN6S+raayNLoX9kjL4Kewegn7jQAnSN0kpfPktGztOJ
Njvn5rWKF2zrI0ogQH1k/WS9wxhmLdFnvkUP9ujMKyX9n24eXOIFPPKUs+8RtPTc
0di8Z7vn3Kh2W0Yut7c1kNR7nZcvWEGW9IeX842UB8gKSYE1FSg=
=eFjw
-----END PGP SIGNATURE-----