-----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/jalu9uZGunHyUIFAmsAXG4ACgkQu9uZGunH yUJriw/+NYv7qRNz8nppewjj+qd1rt94QsVu/fdVNE9BU62gum1eUspKpNy/vpnZ x8P4Pcxxz6foMA2KsAZuOBEmz2QvYMxPjB95p989WcZwX1IWYQClO+AY4dqBMLVH VLPeOtUF1hjvYwke6bht6eeRAtEXnJjbDPJ2EZP1eqlqm70aHzSNbE4QuPyBSC1e 1AQU4aEq9S59tF1xckPaPvrTJXRkPSgiE+19RyQRu6IQ5bgtsqe2KFzsrLcTFLCJ pjI1lt2C61yBieG2fOi4T5PeXAotwXwjxCU1yoFcQWEwIjYpxpMl2jjDR4SAezN9 s0LN03nwaM5Fgp6D1jef8q2XRoTfqJw6wYyd4lRFqv0Stz1pYXtaONaXlHnWqMB6 Zo7Jx/TcqTuVpb1iEG6hu2DC/CLPHC1RKP3LogoDOcx/mYtpj92WpEfUI/8CvRvh h6QR8HZCQhD8rLxvhesQhfkA0qg5sJQ01825zzYBEN+okdLi6Q3SjQHEIVg8riqb 6W4tFDeNeEClCOM0uXVacZ/CXzMG8LZP7GP2LMcKog9zOirMM9rT6Gfm8gNXjN1K Tk0JN8l9PQnrKd5okcN6gcV09JobPIN0i28u+yXA+DrvJi057F514cyTHoYMFQeO /8QSjuKtV0kqqW3LuungGNyo8vgC9Kf4K2jhkSwYOAL+IxdenTY= =TOR/ -----END PGP SIGNATURE-----