-----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/jalu9uZGunHyUIFAmp7r8oACgkQu9uZGunH
yUI6Nw/+NBpAHBDBCE6am6cQ4v7BwvE3y8UowPgKmmAU5eqKeFf00OZTSGc7lh0u
SqohWddYH5fZzjZ92lTE7SIrfUS1ISxrk1hs54+4EtYlOsbVv8RLw6P8NNuvDQJM
B8AJ1N8LIgXE1i5TJQ26bsaPbUuIUdlUtepoGvzFNp2ULKaNSlYrs90kav0AI8pH
5mCQAtSRaDc8/mlbfTFNpftABz1etwvF0fzWFE+PM5yHHc0ayLURtwsFGKwHl347
Hyykxh9PBpf5T+7T+HfbIUBfAVrzJnKF4hY2rq/JrdaxhHU9Z2obxlHK17P4KZdZ
seDXxQo9WAPYIB2QIAFK5ftqRRghDZzW8ofUmlCzTNi1oUWHtECbO3HNXJwz/kvX
lpSvYI76x1a/7jeIj1jpcotnG0D/mo0iWP56qFx00f2RO+GSd6YGlSyvYf7Gru71
381qX+jGMNd6sW1h5/ybAv5aS6OnXXsp8rzbOmP2+Gus1lya8UeBuGZ5gYrK4wyA
nmFh1eRj6L8AU/HvXDOHl3IakOHyJDgYjLxDeGw40SxSYNTTzbSD/brm3YpzFh03
S9X9NVDVsPXFzBhZlJQvPUeBVWS//ve6XbFJndKGzCh/kPjb/2Tzg79vvKS9vXqF
vXc32qVLVxHbl4FvE+31i4Mh01hrOimWMiEBulo0xk/RTCibBxE=
=Zmoo
-----END PGP SIGNATURE-----