-----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/jalu9uZGunHyUIFAmsCFNEACgkQu9uZGunH yUJyGg/+IagUUNfMERodAR1W5fd2WbYIjnzgVnlSRLPaajsAOAtqlq2P3aS/6oe+ WA8onEu6tKhys1kRnyn2hJt8SiHldYH+8Il8DTGeGvrDsQq+aOdc3W2XNlWHfekC 4npyLpCdQKLqF3uErSbmzXUv/P16OtGL+VLTlMY1yeJt8pcn3pSktV5eE3mUBocp LNIdcEasLp5Yo7tl26JjcTwlequ1ZSHuk5UNfv2nS81BfcQf22M+ayipICuXiMme nlGy/2tVuhrRc/J3bMhazmTCrOFz6dNDn/nd2jqiNyLSsErmzLxzL/TuphXXD4MS vJNTLgDmcqcjQsOLhS+UwL8BEYdEO6w84r9NkiWoIL7EKknLFMGZMSzecYtLHjfC vUMVfQHAOuSpxPW1GVjPVM34ZWb/z8NRYOnTDo19HAOMd1UKw4j+TPt5cLy70KDm IDJrVsysTWA1TPqvXJEzes+yaTefFgoL5bqP4+HEYveAee//4V1MpQSPvbrm7b8t sYnfcVzRjU+vSGOW0xV9bD7TTTEMoLEecilpVDKL3tD3VMo7l5IVUNJgFvAZOIhf Kk2xRQIoJ0iSykbC2kBjS8MP3zl/YupqihkrH+sh+bIZm0xdY976UXIRNBXt9Hsx ABIxwIhE4K/8KVG+MvD1XZHbMCg+KMid4MvOxcFcq4ObnCPtAVw= =V7XS -----END PGP SIGNATURE-----