-----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/jalu9uZGunHyUIFAmsBu5MACgkQu9uZGunH yUKZfw//Yj63fnTvQC9FmRKo8kLzNCt8vepxQUrCVYy7ls21Pq3cYxwMXp445TtS y4ROfQusCx8bZCS4YTiqfaBQY+BqicNa3iyu54lVPB5MspJijZSYusyLcC2Dz1aJ nYk48Y8ptV3V/IZDn3R2tTtlzybWeiFstcZHbt9mRjenkWDrcAv+5msDIoKWydNS plHydnYIM030pJNok6gxwRDJo1wNYEEKLIq1IgW1UT+29dvjB2GfzQeCJgkfnCXO n1jJ7ydP5kR/AXlAI+GFu4Z4C2QTTAtNKt2MjtC802vnJGEFTWy+jf7eE6Mzj15U mvMBYzK0Prc+7iqPeuAeT0uoKeGYW+iXn46qNjrF2M/yTIJMWz9thNUfSPJWrCZ1 ekp9qJAzLb1cOHKbzUSUjL76humx7SrcN0jO/D/X4qzpZkskT1qiKYcsNgP0WJgL aWH4n1VPbn1OsotaO2i6M2OxrroxIlULbKRrPmscxgld4NON2rWSjXmIV+uQXXPa 7/zV2Tj+F37DNAJncy/kGduuwSQLPmFNjgQZ2p1gJ0/9fEjVFhtjcPsAS/5ltCBZ R24S0kLO5DjQvGyXvHDSU4NfP8K04i7un28/TscypjR2Ba55QQaaKoGZfaBQrmCO 6g2yJe7P7/jCMA54JKGg9eFnYTk85N0M7RW5LkPXv81JUu08LvE= =LKg8 -----END PGP SIGNATURE-----