-----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/jalu9uZGunHyUIFAmrbUxYACgkQu9uZGunH
yULN3BAArfa12mFL+HMhzBffiDHW+ddh5am22rlO3yWB2MQOZYukm0LFVBV6SpDX
jekGSqFqReg+pUgbgNi3vTuIXn6Ye6OptNALnpb1v079jt5cNDPOauW0YDeEgoTK
YX4pV9Ha9qY465pnNMohebh9BM/8kQyXKhyLyuVYXHD5gtvlwE5HchkxVCERfLgQ
WbXTgmmeT2L1NvB7EFg48lx0b1lgPOELmYoJ5Moxnqmm6q8+0wnsjv8xA22ktEcX
Z4QFC00deTxRtwN5ocON/IhiNdCCXEJirpXm6P6iPQ/xZwPmUC9UjZIRGrfAVIEV
u1vadM7GqTXWIOgzfkSx75zGv9FXO4cpM9cx2/njKZPa9gm8gEX/AjbfHV9Fm70k
skWUF2x4Ny0fnCK5OqKaEGyBg/NZ7KVNHkmHFF5qYrmKtUEs5d6oJVHknj4CKF4G
+Wai9vp3sG7y+AFDSo8Ur4HJJuMXRZS+JhjMxY5gOAh8mKJ5m1iDAO7vn+vD3OVd
tOjguZXzedI7X+9ggq1tZlH7eDvspOPCT1S2igCkoV+mKIDedg/g/ygXeq9IuhWH
VAYfVULmx7MxDZLBZM4xvYgmFtx5Q1BfjH0uVjTVZINuGbtUKh1/eWpCJeClg1OH
n88yuQg+snuQhQMeF5oUeNgKE4FcpmDBgM298/A5AEIYDENVMh4=
=2kCo
-----END PGP SIGNATURE-----