-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmog97QACgkQu9uZGunH
yUIy3A/6A1ZGVmP/fx+3lHthQwms5qToq6KsuEhYNA/SitTUwwu9UYlk38sen3HO
ujz0Ei5i56a8sNFIAhOwU7reUEQC+H/94pdSsPYVnAmsFgqpjTxznJOTIRi+rzl1
qSd8SXkgp3xmyNKUM7YS8v02etn37Mu0HNnulX+lONIiUGuS56293z7h5mfLXX10
qLPJhC4s2JJuvX+Vcj2mv0y1MtaWIXztJRjta2hc+fbw/dSbW5PnZy9pNKBNeLhG
DUuKXAlEQcV9uDvVWbyPtzU0XWkD9294n4EHnbQJVd6rz1wLBgQtXs4c0wtYDcrs
vtjvMkiW1s7sYoDtB3cweiPFHz+bAEyXucCOJrBkj8lw2WcHyxPcMfLnNlhHrcOd
4MsI/RxOtPBWhZH96xtEH5pfiJZqeb2OALvjXUUVix2cnvWCYbcrRkg5LolLe1J4
xY/Kc7mm53Z/EE9C9ctw5hriiRAjYbBQVpcvmWV/h/48sIFn6MSZVfCgbeTWwAo3
1c990o09ZsU5DP9mPHUTed3oxDZj71tjv/Dem2WX9bMT9K5B6c7QpmEovXsoiGS7
MQWg6cMnxf1+xSgEs7DEicfd+0kzE3giVSRhQWaZUxDJ1Cor4a2MsPk07okmv3Za
z42kx/gdyhTJ221U5c6rKw30oMkGnQeH/qeUCeOC/rWOSEtNVSA=
=N+Hq
-----END PGP SIGNATURE-----