-----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/jalu9uZGunHyUIFAmr9sAsACgkQu9uZGunH yULyWRAAgshTUet+lGTx6uEREKwLxwFs6o2SylGSBdYyieUp8OP0ktX7K5B32Ihv TNOrTI9v+hRq9NkwnsubSG1aotdkXWzz+4TLHrIYkzyUnVEG7Y4aYw74CCse2JhO 9kqoBRPaHuEWTZ52wrDGDrUVLqM6IJexxSaA1CjFEy3coV9vcB4wVwoU9k4PEyHt V4TZFvKvarmF57FqOUfe7W46K3gSNanWnV89wvaaysXiWjlb91qC6/kvDEBfgc2y 42+lhLpC5OB/c8pprIkEjWN0i2EbELRdTPfITm2zxeGU4xWIq/d+HoSlaYCQ7Trh WpEZMk3xHaknOBP4Rk2Q1M6z1O5Tve4AwTh+m/WON96qt0ZwuPd3lJ7xBKkn6qaS m/DX2sjH/xQHnwLQTmSsYDI+WvxngtfeC8+GjrwEo0+ZTJ+XAgxJms5vOhS8aSU5 Z7vNFKfPo5Lsx/4jP64Jvhy+VQKpr6GCh+N5mTGHQQ//I8SkAuS3BEzjAOCAFvYK bFLMEaEhbxDbr3QGC/zEB3m9P/2Ot2HkUXtoXvICt+sec5D68codgOg4RfBB4VuO AJmvROgVETvpFs2sMfh6vC5rPX0rnB8npP4kQoFC5wLJzTsWweJJg6AtiBKEV/0+ Vi0FnAfY3eJ9ah1kTeBvy0wwe1ZFdhb1ECo+UL1MtF0Ya58Xzig= =Zz72 -----END PGP SIGNATURE-----