-----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/jalu9uZGunHyUIFAmppmy4ACgkQu9uZGunH
yULNaQ//Y1WZHwC/NeoDOmtfhLhAv2Lzgx+tRgQJ6vpPLvLfPcv/J+Osx2P7W5Xi
MI5QViGB/VmXf/RxNEG0MAh/Ccmr7a3fpBTR/2VtnNB7OSqmPwYwJt5LJsMNqDzM
IaduSA2SlNoW39qEoBXx4izgP2gYmWG1jkRuvWgjgczNqTCh6rMh2+uLdItSp+i3
9ID8/wfMdGxnBuNdxUjUMClPTde1bQ88TgKNfqnvMNPvtw/bUf6o/LJn50XSkXHg
kzQ1G8DksRUl9zKsGeSznXR/vnHFMgA2bBrENxHtP3aZdHQfxutWBwGRj8wbT3Tb
Wq2+2QNJtkeFTzfmFci1ZonU4Dx258mVIMUzBNNmP0LfnI83UQWIazgsFieYcvxj
tSss2Irv1h/MqUu/XIGg/pH/9SqecUkpfJvfoGcBdBNIBsEsminVRkm6iowkU+04
K0ioIVZB00UOczVfQTMn64J1gk+fvIC/BIiw5uOb91XweKnbV1Zc4Sy2lC+12ziy
uKtHEl16OSJrU2FucGyutrUAdczFf43FkJQO8vDyv3JnVP/pUJ8newjULST2nmjo
1vbvovxe4iyWy3XkL+FQCDOb/Gft6gSBhyDYth6X1q7HxbNp9M+ss+i5EJdyhmTD
IOpP7guufzxqnE2WI8Fb55G99twShavFnhHQ+ec9C+xuFn4Aw/g=
=pePt
-----END PGP SIGNATURE-----