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

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrmlXsACgkQu9uZGunH
yUJfsQ/+NWjv6OiJl5qQiJ64AZTMaJvjV9AFFzqDp+thIpK1q5aa4Zs6kC64xvVS
8pi9wLIJeDMToPrxswF+m49YppS2dGXEZgWRupp62O224ov9g88yon5yW9nlPDWS
NMCe1eKN1gcBz8FiOFB+UP4+LrB0ZKxAdrixgaFquqGgC17cFD3wxyhcjJPKRs6K
EsqO2SvLmIXw3ZyJ99ZQ+MLrMihGv+UfliLn41rP6+2ER5W49IG8eak1eE24q4cN
IPt93/iN6sogD6k++mMVTS4SNOp1crJukuevjgxkV5YddVt256U6QhXPe5FIbJN/
Op0LAve/gWLzPc5yqfaDmfvSHLJW2cc0ufU3mz7O3rIGRw21MDC91fqK9KS1OZRU
3x4m7qhVwgBVse6bodhv86njQ9oUGmDzWxTlDpLbwtoUxkODxHkYV/IrCyHlLPoK
yDQXH+1ir0ERivDAGmGLjltUnAhSzabezPaO1turJ4glQKKZO0h/5awbrZQMaJ08
EHFAB26BTpTjXWE6t0+xLZ5SpvymNvPMDf0bjdocjO42+O0Dhwi2wjaNkUU4lQ04
ZaQSTqmMjl2TokctFwl71XQSTnJAlzwmEWedl3yIHUH7bhI2/y3LQr9EMCL1FKLL
HPeAE9v0QU3YYdtPieff8cxvQmDPI1kaEQfc4AfSbhVptad/NLs=
=i0mK
-----END PGP SIGNATURE-----