-----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/jalu9uZGunHyUIFAmp/2pUACgkQu9uZGunH
yUIePg/+MM3JsuKuQ4CZLHcpnkkXp4PfGZWqd8u+9O05C+X4qK2yjWZfH9YODkOE
bHvNXKB/0PykMTYEos0+el0ltQ4rtmWAL9eSQt6QGphO+PL3xgYGMP469Pr9DG7m
3jlg3pJ4Z8d3CYqSlG41jGSRLYoJ7o4jk9HZck1gPjuwBlAVoZ9gHX60qHROFAF/
GvVlZyu5BwaZ81mDoDL2qcMKVPXEDWcJv53DHwXJ4ExTITfPbvrlFolCsOIjaxaK
0iwrmlElB6evXuqLWhqSciKj+XnKpX21p+WLlOCyVReYkX8VR7q50RNweMM80abH
dEOpEUTn0OCKKhRliLzz8F5nEgVGHhykE5GEkXubUD3zxq1Pcid6QUJDRNqznUae
0u72YzcyNEWAm1ikFfPCHNNWBH3HREJbD6KPZm3rYT7SgfduuKO5JpGNJKR/ydsh
FwwNtvwRkhlhLWNCC7fn1Up6vbRtSiIwBiGLvcHwNVqcF616nKChCg6u1fwc+eFz
aAuUAZdC3z8GUwyanEVYuI/ZARRbqObqDFcjx/KN4gAeR2fKs/6YXGghtco7eqlZ
w9y2XEAph7ABjS9UVWpWGNZ/DUSU9ROq07MOEhecPP87rW0ibxukEaspI44nj3Z/
TPkLG3zBjsNxYabdnwo7uMuz6Cocwrd7hcG39c4r9eeqd7smSTY=
=sOIK
-----END PGP SIGNATURE-----