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

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpM1N4ACgkQu9uZGunH
yUI7Vw/+NuIPvcXx00ji6z5x5pOguH2Q9p03OpBt9GA1Qm9e86yGBESe9AEfrBB3
Y4mBHSQmlvy2uUETc8F9IFcTzFZYgUfkHedA2BYKPcxX59G3N2jfGAWGcZC4mdYn
272mZz6QvedXcIL6+4Ry94/1xw3hviTPJF+fF/6iPY9LuF8cEZ9XdG/FgiCRvpEy
a/URTz2knVV7H3lw1vzgfcblTmXs4M+sx1vqQbnhXssbtI/EE67FkLBOOVnnQyFV
Y0cPepkXllwQ/odQBpQLAbYNjfybEiMGHDJtn+s/KNW0z+OmYFKs04PVCcMPAIYS
qpxo2PnM0HXb8DrsE4+PZI9NKXr5Gn4XD+u+2B4t95r8e/SePRSz7/QQq6ql4Qr0
f9twIFqHHd8YL9Cqd8E9Tbm3lCY4vdqltWzGitus+r7eWA4zNrs6Y/PxOw5vSZ8g
UTt9LHWPuX18/zzELvutlpP0Afrzit5G2S2pq0R1xCme4mmKSP8e1dzxPASyBYy0
pi3KTw29mllpOW79UnymdmS0KjNNDSP5ItxCwn4qkDLfhPKHSzmyUavPZmOGCSdP
R0qUgxpi/e3f7M9xDzmOQD6PwCGdStJZbcnD/Lv2p/+Obyn/uXh8jMzVdwYTcVOc
hU613wchwL8+Jmo5Gi3I4cp7YIvWW7oKPjxGjDW3HU96oQpVQJI=
=/Reo
-----END PGP SIGNATURE-----