-----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/jalu9uZGunHyUIFAmsAwIoACgkQu9uZGunH yUIEKg/+Ifni1WplINFNoMmmiQA+1FLUIJZBrq2Pzb2YPxCCaHUAmspZpKjEob+T gtm4Q1FWfqTodASxhInFUpgDItKScYZYvDT9b4PAH+pp35tqYRYhORKEO6Vp3G1N RAodNOJsA65OvRChEYlB5uJDYEIDr1GyaA+oLvx6Zl6Lij/DpAZf+mDfkEtBge4f wlPPE+FuW6yBpJ4ug3ycQ7zOf2ZDjy3CThG+Lo5jD9DOKoGv2lq2i4Maq5nqH1jO PJgZLmztDqChQc17njO5Ac1QHjS+gIcUiyVLybDz8f4JRosz4Y8fPnYGnXdSLrbZ ymJpilCjp1FsHB3sitMQXUYlTJzTdA3Xj7ptz7n4Ds1cIzOnxi/XAm8PbcfRlCl2 S0PThnW0rrzn/5qqeZHI5Jh+qbcciVQaHYRbz5odEfWVbf/sFxThq3vK1bpIeQvW AXfg/lcnxhpZ4oo1bx1xnPaopyBiBnqRyfU/evwpe2m1z0deEXeuhupKQFp/yeBW su07b+wTjca6CwsHKucQZRFfsV2oW5G0V+x+7bRw9fTESO7AiNt95ChvIC7LzmNq sIYOpr291jBqSQb8+KgtR314pUYy2sfiVaWEZG6I1+fWE634hRwDVwGsStlTocEC r4aokK2XePBTRdgHRH7vxpj/m/+Arqr3QxbYC8aBKZqnlloiuZI= =NQls -----END PGP SIGNATURE-----