-----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/jalu9uZGunHyUIFAmpx4+AACgkQu9uZGunH
yUJocQ/5ATTa5DqBAbYp9Bd78glG41FTi3/fhvpIXHUx5EzRhmfod8QW1k6KP8kE
qFhrMf1NCBEqgeHJ/lAtoHysjoXy8Cc3xrUi0HLVKa8BfGZI3nWvANSdKQFDdcqU
SaMgi7wBlsA+jjYVriu1OTqKlIL6LcVNZ39GoLqkfz422VhP5G5uGaeXzVCdBWze
vAQtOZ2inwyB2/iKKMYGHPSOI3CRkWl5H4Fs9lpDrFg4mnsuyXlgpK44DwgsltzZ
DIjVLE/xj8nKMVdihIYOwbMBPnGLuZbbAbm6iMiIzjJsPl1PV5uZA2/BcjK51KZr
XQcxpitPv9LRmuJXVfuBDAXTX8uT7rETiF1wCE8FVgZfuqoyq7upnukFBH7uOFie
LdgqQIxvgpKXs3Gz3l38U1mTn418damtBf286QAitE2nOsoNwxee+AT04O/yuG/C
x/2gbBnpqyldxFKfwNau2VcWXPVgMWoJCQ17q03lkPw2/wwQGFfYBsn2fXY/TcF0
LAnGIAaxa4WrTMHiNpwX5ukxc2To1bISH2AsCVusePFqD/4cbKr+If5bXdV4npFY
EsOSxHtDZqZGzcil46iulLkMLpk1vmUEcOQiuwFb05YLNT2hC5X6C6yC+d7SyARx
/RQTuW1O94NUinY69BTvncbayeCytNNr+TSpzbx/3WJitwK2U70=
=zRlt
-----END PGP SIGNATURE-----