-----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/jalu9uZGunHyUIFAmr8vB0ACgkQu9uZGunH yUIBfRAAswpFrqL87XNNjbr5asm9oW5gvS7W8zt3KzP+adESZaxMStM7IEB/JMo/ X7HM/ZFakDAXDQjL4o8/1HYx/aEKl6dV0qiVyA6Z5GzbuGqTdcW2HWyvv2yuxbXA Fil5pxYERqfwdxj6md72iBzNa9d3RGS3Rn5ag4NV04ZfBHTLZf1dZ6tlvWwUdnqj gj93KceRD1t36p1FoAC/Xpx5GKBNDFCTqpN7h34SAIHgggO/qu1KwNoaT6S/55Vh qaLb4xWM9IwuXXviPG11+1C1EWOfTKX6Gxsqkh3G/avpcsAO2tFVmTKqy8k+Ityj ME+KpIdI1UVuJ/FoF0rIZgBdW/BmiIRxcC6J/Qj2TQSX84Dv2AgYWK5XqZlR9hV+ 2xqFfflj1sNobjS3IbAF5+6M8/x2Dh/E4nFrC3em7dThfB9eeHdsJVErukPqFL2M UeGgzDDPoTp0GKW55EGxPSEMJ/Ksx+acFs5H5VLvKuGE7b65rRgS0q8n/dC7vJ24 GOrUyh5cR5KuDlbYhXbEW7JKSTnT6K4H/xavR6rX+WXrMZp1Q0VjdvaxgbCVMHFk xetR65A7Ml9miCIAGBQV9vD6OvgnyCu0nbLUavESA1KUEL9sLswlr3SZP0S/ReCI igzqqo5RBu0/JYA0Dm1YUe39DHHe77+s3QF4bZBunaac8pCEzZY= =YF1u -----END PGP SIGNATURE-----