-----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/jalu9uZGunHyUIFAmr7ZyEACgkQu9uZGunH yUKX5A/+OAuRvTOnaE2nNnCcTxJrmdSD0db7QonpOGpcpDt0TvjH7Xyz70FnzkBj rBVYRubZSpaV63yueVdkb50WiBfTlU907qqEizKRy5kcMNm53bFhHa8WUxGzNwSh XzQa6/fr44u0+cjExJu6HOkCoJPluZvKK02XmeBsf4Ae4LRdk12+iXvt+tuXirPO znNW9aujSGXmCfBz3GJwi47Omax2C2rTmtXNlFu4bJy65fhTwWs0jVX3Myqud7WV 2KMmkQgf/xwpAHbKvDVzPBSCte9vMStnmIcX8Fqd2sU4wW57TTULY4Sei09bkktg H/+2a4NhmM064vtwubgPAQktz4nAcf89xzC5HQNX9T9UM22L3D1LCqA2eEvpsdeU CWX2z6Buw7f6K7hg4uXc6dRQC8BSzMjEHDC+1+g1xDAGB5Ne9XPXjNMHUon0y6bp L9018L6PdTtdQ/fz9qdBLLGlKdfgYVuJ4541Sn5NCxilDBlK0C5ZYNJ+AeI4ujOU uLnk5YtiLwgMeXkTk02gxFY+0DHa2IN+YPSU3UU6MhzrruIqCuXbIns5a4eIh7Ks q4jfKGMBwhl9rh9Q6X1aiEtk2jhowiX5SSId4dz5RilwykeYz9Xm7kS7H34oAeqN JKOWvmBZU4PtlK0gDlQ5VYjTMXEhuEzjArEnmPIKP8GI35eg4fU= =9nHp -----END PGP SIGNATURE-----