-----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/jalu9uZGunHyUIFAmpoQeoACgkQu9uZGunH
yUJtHA/9FDAlnQGc6ogFfdRGvMEm1pEhPc6VHpanAHpqbbUTUobqSxQcpQ/Bh98a
7YrrAY1jzQmr+PHYVHIA/a/iQ33+AFmZsuT7aGSDmHNFuIVNbJMQkK1+3r1mg2+1
2NMsIcaNoJkCR0Kx/jwe8AkTT59NABc1yhY11pJAHBg4T88tOti7YcF7tGhNXI7R
xpw4YkHODaz0XDyiQBO/uoMFcfHPd4e4E8KmaMrPJPDut6iSmVPjhZTmaJLByS3p
JbHCavYcwrG7qh+r0slSfwPQ44bq9Jl46uUdWRoqPt6ng8UxLy3klX0OeuSXPOS3
mxvCgqI019Nr0viF41KPHiSXmq+g137mre6Xt7z1niTl7Ea8Ufr/3wpIdBxwE6Ue
D53J1d7ldEMe45pjr/y7fVrdZhsS44zAMvh57EIo4UiE6FjwRll4jVWdEfXjt4Ms
mlaAmIr3gxS/2KgMDIW3PiixZZNDArvgrYPTl3BrWr+Y5jY8LHq0eFpyiIusGZc4
rPczhRXMG4etziGcaoAiF4TlcKTQ2zefsC69+5bTx/HprvMR+7VLRrUf0vhr7/JQ
4sYhR5C6UsstqiXnjGvWSS2uHcSgrrXecJ1KlZef13Frkx8TxqsKwRYbR/3n0o8L
8pG2qxl98kZXNNAjdlFxWapbKLiZllh+P6c/15YbIqMh+v+BWzs=
=Bno7
-----END PGP SIGNATURE-----