-----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/jalu9uZGunHyUIFAmp6RIAACgkQu9uZGunH
yUJe+g/6AqOstiin9z9/rNgQ6fl1GCxguhZL066wIf4O1wdKmOPlpVi/3ZlJz4hR
pXEy4o0IrnMtqQ4lvZZVnVUpBjfAVjFz6zGz14s9Ztojgsv/lKk/yALmQZnKoc+J
o+Bs88MUuOKh/jAPIAKFaRN1KaH93FAzzSx4ZSs6tP+lD6KfemHoskHCj6AP2HVU
OgApS3gzSaCTVP12n9EcN7yx15SH9K4DBW/FyPZ2PvaEZjosJOrPFv/nHpQUU5Sv
5hFanhiA21X2CV2zcsW//gFpn7qi74V7RPi5wUyeP37ArzMrycRUGgkypUb8QhxU
zN+BpuhVE7/YaHtA50zIFm1MpASeIcJj0i7as1gTzFeaxCVT0oKJe/sa3r6/FELR
N7q9Sx/JOOssKctBXYKGuuXv5Zkg0TD91ZE64VcG8lYPxLkXCjIMcav/w/wp/TTX
Z/A5JuCdsztDOz0BubY98LRDOLn8jpDhmQ9GR65QAcHfKMSfg+83vphS5pToOaPg
zL//WEQUDwP/wyc0IFJBl3ffHc2ObXLv6ad/4cxk5QnCNZ3Rsr6KTA1uAsvorQhs
sZBNR828fCCmvXD5n+gCKYtWjUbZtugwd8R6uRrusYXocyd6NTLfVc51OlKjwpBB
cMosL1B1kY8h1FtMlNNTapYjQASX7ywz8ndR1yN/6RFpAuBJ1tE=
=scUE
-----END PGP SIGNATURE-----