-----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/jalu9uZGunHyUIFAmr8V2YACgkQu9uZGunH yULFWBAAkLBOiJwpsj6JeBp2d8InESpiCJq7cp/suifJIWPnu/DsblIPlawLSmd8 CHgQB0XyDxs8SxCrrsMCCjJvrWPniax+Rn/sH/wuiHXAGJe3nqLq4fPv6NMi3mhA 6U5IA71tnN6zZs8NKcg7JWbo0L6YxRY20TJU9Nb+LGYtLX13FtqLNnSH3vLBH57a 4pTVei0wsjtkWZJqEcqD6BPg6nEzLQhPwGFqv7hBQt9NG6VcK79b7pTUWp7xIPDv r5+QJyRtyXw/dLH0Yy+weqCQxOuoZyEKY62eAqUpYUOd0sDm36fQ8c+sLu7+nBdz ybm9fjQsQ293RwqvyjnsrffILbpTU9KBXpjjClfbIQj9BRJguqVSb2KMWPIdb7Cf iHi75lqT/KsgzouRIfpSJwtUG027zpbLLGQb0GOcjKKD9b5zHLmu8vY/9BxNRejn 009a5Q9Aq3BGIt97OyXcd+rNxKT7yPIY5OmAwTlPCz4jDXQ0KbpwmBF2wEUC2O6s +bTL3R8RvqJcB57hITWMqPR8DJcT3BqDVcysflMI7xzk1OxS22dZFbQyX+zncbyq xO5KEhryXml2WyRsPd1asmjeZy52AzltE5kAIQUAHT2lCutZoq7DPPeA7sg0jA/R GqWYsjBcmoVQriQCwW7UZ4JFbTsZKQeN9tQ8CkUe1tOcjcIw1ZE= =FzvJ -----END PGP SIGNATURE-----