-----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/jalu9uZGunHyUIFAmrMWdMACgkQu9uZGunH
yUITAQ/8DJ4gtImHXUsRlpgoE8r3tsF2/3Fp1HSrwm6b6NEOlVaiUrDGDlK8J/uh
GaJtjNOzzxOYU2ZXJ8XmxkXxwIln7hT3xqIkKoCH132aIC75iTeyJRkDklbt7SmQ
M9wXYB9q7y/TprYP4PcCC19UOcvcXwdTVyXivRH36wD94OYflB0oTUc18yzMzBRt
9cFWCT8zMAt7b/u8t/mjSkZUfYu+YhcHOGw3XDCm0nMeSw4li0oNvtDOCLrC3XbU
AWwrTHSTcZCCrmHHnL1Z/jIw+rOUYmo9xkuA0n21ROZ4fOoFqn+3mmyiYQzmflO9
oQrTdzTRto2c0VvYOdWujJMmboz4rAw8xwIPY9GHFoOxiUqbfaYak/dK0gzJEZyx
TgvYtBPzdnuxBFjl5HNMX+z4s/mjz25R5Utgq28GvTpL0+dtegYYahsaEUKNcgbJ
pIq2R9P9Ng+UmIU65IUDwtrqA9ZbYzyF9HiSd+gI6cObEoJ34w1ivuknkLO2ID7f
+F8tPVt37MbFxa0WQF2BKQDnZaGdXmGwvDEys6nwCL+2mgosCzFiueBj6v8QLgfY
WonIxy0YlAIAjgkJ5hYDnMu3wdGM11mgdAVnSlOoBDOec7O9v8Zy0vf7/1u2UY5d
Ib76w0kyeIOGnDh0R74w0V2ZcreimEx/SB9Kh7bA7L5PX8+F1yo=
=sjMb
-----END PGP SIGNATURE-----