-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 md5: e278028e50b73b55cd6a06d0c5bb3524 sha1: dc11ccf4657fa4ac008ee5ddb89c27e40b7477c9 sha256: 2ba029d1c84724f79740c0296244fd6056f12aa1be1925134d9141f9d036ac0b sha512: 279bd76c4abda7efcfc181ce35ac993a99a11d60d34283d0e7b0d15443a6ca1e1c6b75444193c075f865bfa0f8b574189e6e91e6980b89ee767ee5874b7f5b4a 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/jalu9uZGunHyUIFAmcnOboACgkQu9uZGunH yUJ7/A/9HLp+NrPumXGAY5Rtr71tWHwQ82EgIT8c/3OOpKWFClVfew9T7jbUknUq i11Yd8DwnOmuQnctB5VRsI+CObZ2EVwsSa83s/U3kt4yIJFtK3h8mOpZUDK+lLhD f1HY84RfgVuwO/RMJ0L75JHJnultbl4eUkzL6M0lCtdvqTTyuB/8xK2O2yYNpk6I wC6wV6r/vWwDC0HNt1iyND9KgpxcECSjtIGomc7MPNqP+tLwv47nXH/UEMLFqH7m Kl2F7gYGe67he4IIb/YQfYOrEKRzqWj4SuH0ueUALSEGu1VRMnFlfIIuV/6lLXOn D0q72b4T5Pp3lHagUEEEvBEZ9pISpO2JxaFW2RRCNa+I02SzARuZDmA2JnOza8jR 6MugsC7lWW0MJyOONzz9DUyBSDNtQ5J5pMyu1TkR/oVdts09DveN+PeDyYd2y8Qi JJ5LbExkvduj5xCL+mpyYP+V2oVkEw/NHF3fYDb0a6R8MuHcOH+x5x3F3ZvVWJ7g NdX/rQctNOkKA3s8hfWrR3f+AVOViurxquKjWATQnZxUp8QME7AndzGVbkJDuSaA BwClyt1bcQJKO3XHRi5upWeG9UnZfWc+1Bp6fZVevyONFP41Kwx41+AwruW7PhR0 h/Rd19O+Jvvb1p1jZ4CzUNm/klIzr72tSmudn4LCw6aNvu289oc= =8+6H -----END PGP SIGNATURE-----