-----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/jalu9uZGunHyUIFAmqJbboACgkQu9uZGunH
yUIW6xAAk1peSsdZvqyGYUWBcAYXHnamRCAYROXhW96efMFGcO4ip9lBPQ07U8vR
vFi7RP1zdKHLpPcorwS01GDL+iPVGzS8YeSnkijDYPXld04Y/dUYJppVtU341btf
qlQMmsirJK4NKPA2r7O0fQqKaHb7lQHqhpHCFIgJyEZG3jcRv0elhcHc1/EmuEDx
bl8D6ws37PIy7lZ97gNRSdOaOQW8gHFTRAqmYmjAzLZsorxqlMCmdwGnPu2x7fgY
5X3VMjhvds4TfwLH97uxcLobotgfp3rhjeUDCkKzJyr0YEUPQ8D9PQHePuTlDZra
fI+Ys0jIOjY3Wev4dEwYlqaQbCVkApz9LdnjZq2x7sJcVTyUtiH2pzNGrHM9MCnP
hNP5YrkpcXXoZDzO4hLfSe3gDBMOOurZ5DLxQXVmORn1RLcG2eb34x4l2lje09Zf
10tfxgWYnSmlTpKeIHE1rQhRH0+WgTrm/uR28DNQdXFv3XyhJwvNZqKHOHQfIUyV
HZiduxkUTBooVVJiqV8wVEixGxQ0lR1u2SewOWXkSv8UkZSdz9MUt2E4DZ7u3mZo
qaoEm2YDCzJ8w+qg1PnhEKfjHquP05cdwjO5xSC9D8RgnEVuIF0npggBIQtYUyWz
F0MY5KDCEcRtAsZFMlBkmmzy4B9vaF76JbwUoEpJiRxr3PvF6wM=
=ktvF
-----END PGP SIGNATURE-----