-----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/jalu9uZGunHyUIFAmsDI/YACgkQu9uZGunH yUKyYBAAl/cp8Wc4mGt2XGtgQACUBLhO9bylUKzPDlrmnJU5Wy51bGrjCjiNFddu szSZlYPupzeKKO/pUzwjOpTtiVZaJ7iGxd/ASASc9lJJE36pSg15+9u1wB91YDRV JxZ6hojSOqzCLOE0fgTtNN5OH6MgwXkimzCOszlRYDd8xC/EBm9wAZqGvdcOfK8I 02dyEQQI9qgAxMX7eSWa05aBN9veIImq9/VpyuoA40qqDw+V/ZTxkG9dMRwM82hh naPHcx7VGwyxUwMNpYvJdyIPHRMDPhyy/RsQm1w92UI/eMwukiNVZCFvR8bu2t+p aSCefQ6uiUP70/+7pitfUs5ZFOaxKPEOdRs8M78bpPLyuv9yRDYMEsrCLYysPKQl 5WR7ZrjeKXxmOxxpXypadwB08cIHe1vWsgksJf/rqU+/QeuJJPsTh76azolGxYTS 8rSqNsMbqH03x2JvCEKKYUiRBDku73OOWMEYewBeM0h0fDHyGEZaO0XHlJS03fys UfIy6I4NO5NJg5h5/NXXSdm0ilCNe0gxqdOSqOp+VNVDH12FPtesyRs98OK3vaqu d/3ybqIw5ADdcHR98nOM9HmhOmxDrPdCcJOzm1T+bsMFP9qCZYd2YLArfIHJGcn2 HA1xJGy9TZifxUjVcWtYWfxF+mgTOA+UQM4PQF+Zt6ViaQtqMc0= =j/nU -----END PGP SIGNATURE-----