-----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/jalu9uZGunHyUIFAmr+GNEACgkQu9uZGunH yUI/Vg/+Kibg4c1CVyV4Hn4Nn4pXNedoZ06nCaRcBG34Vl7jVE3PLrbA2xpcIP9e BQbQOjMWFPDLscrM+0Jb4UBakFcSgI4rLdDe+eKDEOLUzjJZtT6MCc18cB6QTlJV YAHuibIWF0O4DdCW+lZTgUsy/FHtJMq31pzT8MlNaosvScojYz1w/ogoTRtxG/EC a6xRo8+uSGnqdIBVU+MnebcYVeDwKqlrinENIIGJg185sZ6Oodvps3muR3hFMq0W PAx03RIRWaRhNANwzaN5iJlXgkcqWVM7ztL0ZkVpr5oWfNyVwKmxFha6IAmHQrD/ d2RLFdymhdEmDy1r2pSNJsrtv4IzJ13JTaXPJ99Q2pLP6YrPb9SN9HkNUuq6CBFS Qx/MHJAT1FOUrJism07cBAuSntCiYiPaYXPaY/OV/s9jpogPBmUnVRKWdgiU9qH9 GII0ECaSX8T+rQoRd/lbY20G5njRFd8eQ9ger09Lhx4qya4nDviptZvxC5CpDA+f H8lzs59D8l7eKrV2IXmiPxfsi7nAs6ZYiM7N4YZIS9IR2la5eCkwQ6xpOJyQEmO2 J/Ir6FK3oqsle9416TAvSLMiIMwtcMe1c+6OQ7ZuO7s2mEU1b4wOfq38J0e6yXbj iFTlQNeUdKd51WeykXdgE2G0nmndw5Z6eQgi3HnNBf5/EmI6Vaw= =aYRL -----END PGP SIGNATURE-----