-----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/jalu9uZGunHyUIFAmphetUACgkQu9uZGunH
yULkNA//fqXYdWKraKPG3cbnd9vaodWCBLPlZGGH4xftf3/hXEr5owndimeBF3gj
7+Gpz3xFvKtCkFNxBc3Ix9LtVUChtD6Ve3LKhVghseCP4igUQVPAMNTHKfmOU2GJ
ZmatWM80YFKhOnh+ZsiPs0VNS8oqfRqZmhbjYVkhyqO4PP9p8uXKQGxCBTC7tdEI
KIA1MIZovstD8qgHzH88Xri3eezmgjnzRwQwNDd1ZnkZpud7NTXEPfSaVbVRV2mH
sEA4PL0eugpdzeUq8+SQOL2h02PgtEMyvpgMuqUX/oZYXkChjwxtO82zlbsSb6Zv
ht4QzyuOky92yXcAqHWkKVgE4rV5UJAqL77yLh/9hwICuVFQeKh/QuVG28Z9CkEF
VSGU5HU87sgLpM7WRyRWHHCxlBRu1qrWv3gRaQeim2bvsu9cSKS+gs95+7Qg1AUv
1IFNEMf/xFHsYe8CQXqM7gFa+FEo6ex/oD6TXHSY2TUXKdpOA8jMz+DbB2Qn1CIU
rDLTbuEnxUzzRhwkG3mqSjT5NkQJVtoOXMeIrmmyd3pqHi10kAWUi67rTp16Rk5V
1Ky164zkpE29VGEYhvxVXxVb5jwPIxSKfJPjnWt6RhR295dKSZjAYoTMggS0/HGd
quuzY5nTL86n5AtLUe1PW2Hari2YO/4jKEPTEMjTH0o/e/LdrgY=
=O1cg
-----END PGP SIGNATURE-----