-----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/BF0ACgkQu9uZGunH yULG1w/+KSFuRF+O3OsjW1W8DS94jPfyozSlNRnTe2+zMHOFfw8FCug10Tu5GeTL 3SXhwCdMSvM14c6qMpjE4zCIyQkdRNf05cJIm/uJDw0q4AFyoHd3gnSd4KFbubev rifArPjWT1Q/bfbyZfyeNUkfgta98qQ32YMXhqAiGLvifuzgvnqFr97eBrcKP8Pt uzTOb1KIbd7Vv8ScygTALjRyq7EG90f5yYe/QDCdmI08P8jrJHfEXUnPfBijWuRa GJ7z0buarG6TB4uUD0we30mWxeroOSq/a5FMAdCN2bY+uFxw7Wz+7WUIPsAizLGL dFvBIjqTk3hgEsKDzIutNWhxOIdpFO5beQJlSBq5WiJpLSWpX6OaPB6bEX/L3tsB WFHg9+aJpPGxqI+qaEKTOWxUi+GDHMD+5IcVV7H4+pTEfi+xmjWixGQe9VFpKKQX 1uvjKmfYEw2b0UqVsPW19WIYOzjirrt2S1gRmTvmInD+gCLFTtCAifIcJztnqP89 ZFY4PbHEL9NGdg7TS1TQIgVxzM3FXkuRWKE/s8S+6o+yEZuKCurpYjxTntgebkce 7kZ7TMcjrpDtqRDheHKle8iIC1JC4++eJbGiLSq4LX169b9Z70lva+9pEnkuZCdy hty/xQHRXjJt2907kLlgrmLxsVvMVnqtY15ODPVCB/WqPZYb1J4= =C6P+ -----END PGP SIGNATURE-----