-----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/jalu9uZGunHyUIFAmpvHQIACgkQu9uZGunH
yULvWg/9Fj2hEqvLMY3QyBOW3WD7+oAJEtWRcnETmkx6K/SXDremMbH3HqEOehQs
/en0HOM3Lz3txPDTmMWHE8hgQea+mLT/3nZMBCAfnsTIMUSQgQKFiaV+22UjOT4c
zDjo/HBJkw4Su13AU3BblmKgMlnTq6jvQ39omU0SJ104Hyy0ao9RUauIS3LsqM7Z
FkWL0UyBbZecUNp1+851ZDCFgHDYrpajD0Boq5cU/CehXXZ1RgwLeI9fqgkUQiyX
J3zRYAStDRe6cSv/VVyT7EKiGm8Ojsi9lrgF0oyTbMUJc5deh1oKIxLcu8A4iS+W
452SLVv7/drIc7CMEu5UqZ5CgXuJtaCHn9OEOIBwKTViLCV/fMYKx2gjNX5smpJG
sGwrpW+nBMLEqmGZTQPaYcN5xQ4GHfmxB1i/URHxdTUYaUNwwfTa/vydOxwruRJ7
4YNy+Ojgx8dpHPgPbJMnCbT4AQ9iv7mlMW0XzwxQttqFC1AbfPqjdUchH8nNwQwb
i1ufXZugw2tmn84zO+Eqasop4ADYBl/fpzxEG6hUAnyE4VEwURwQAnR/nZnVlFMG
0GnLLf5rC8Yh2T30j7s2kpbWAFxUGKXdqETmnfGoo0cEhOB3btk2R7nZjQZcqzyj
bXiODUofX0/CIB01COzJ/HaXca7PygczCpGAmJ06QAtWw2d/gSk=
=a7YA
-----END PGP SIGNATURE-----