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

md5:
3613b1e032d878f162876e61acebe5b7
sha1:
1f3b5c0a51ab4772e8b68ed3ee25386f8fe8dc2e
sha256:
045c8b9fbbbcaaed3486f2819f9a3d9256cd75b603f6579ea1efca16f0ef6383
sha512:
d953f92481a2cbe0371f5666aaa4bff6e725234d7a5b21185fcc9596c33a4add62b09e4ce01b2f4ff87345dc3d7283056e3114ef130c7ea8af6c642ac5fcacfd

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/jalu9uZGunHyUIFAmqUlRMACgkQu9uZGunH
yULZFw//fOGfR3Tn1GNRulnrZ4S4otFCC0A17hTxh0IAawvufB/oREvalBcaLAee
EOVO6KNDeZ4tphRl7RX/93xQ+fbyla96Sl+vl3iThNqpxSvZIzotoAVXwBC3J5tr
wpQ4TQZs60xkUN1FYn4dhGk1mtvZodP7HKonN+Bt6jTtNeCBnDw0yIfTbIRK1M/s
KVxxL2E6nD7PAhIcgJpVCvN1vU8Pb4zuiSnZ+LzwgyOUk4WcBdN/PPgnfAWwGXj9
+yt0pUaMdDqPQ8hLHM+aOfpASsvSTnENKBg5tTG7xNF4Fuq8dGJJFCiE7f2vgc28
6Nsyr1to6u4fKgIdLhSHK028UpDQ7ic+geZCpcbIjXHxUiVJaOvB9F3HhQyBRkEW
KeAuRk5CYCrErQOWh/u8L/J/yj/Yp7DeuhaoduViYJU1KrbGw62seGsHVW5kyYmL
ipejU1CeQTbYr1y6gN6QzMquz/326q4cgskqp0XKNyVQXH8uHk7wz43YTQdEbZBc
YNpAANFYbUKcWPlImGZ9DW7yX+u0UYFa04lE6TSObawRIpkiHrKtiJpLQEbA4XD5
dm+yss1kbGW86NpLUQo7F3TMr+Qn4HnzBRWdeeQOv6+qv/iQ429AvTfxnynnpWhi
c1jTTO/n5+2jp3+ygP767kRtCeN8mKUXxr+F5cxGsnBA1yJNA+c=
=zu+0
-----END PGP SIGNATURE-----