-----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/jalu9uZGunHyUIFAmr/bS0ACgkQu9uZGunH yULp9Q//R1o+VFOA8gMhFmgw0KRWtGH+crs7m/PqlO6rYzzyh4BPCrm3CV9z7pkf k/KVRDw6boFFEreMsfPJqpMr1B1YbOHtfTIRFdJtKPTwoG9wpKSOSSAjSWqtIVGA PdxxgyMkkyB1EoX78ONBQCiuWs0Qa1FdnuYrUrbJ5sfoeqqnWlvVf7AgQVoQvjh3 C+P/NDb2ds51Bus0T6QkDEEPOEpGHcD9+V5OnXj1wUWhHUA2NPvoX1fP7e/UmFJP Sa5J4qNcYxItUEpJ/u3DCA/K0C2KG1pq1aqbP69oExwScbR2su1SXxV7aqNXC/KZ HBDUtjAVcy3TD49HYG/nquaEtauJGmYLQ7GnMVgEjXnRakS3fNf5zySTXn8fbU8Q pIFDsoQqhoUJ/oGCQg+O69sbhBDCgjzEo56G766L4sGKrkufW9tgG7z7x5zhzC5T QMDlHaHaQ43Gk/Z93klstCJEUanRoTsuLe0vVJS1R0UnF69gZKlZ36BHd7LZ2Edm E5Jx74ckTHWtXPiteKvELBgAyFSfMkSSDz7pMsswW4NtdzcK7j6LrPzRFTDKgAFS sKDAUHsdnbaLNGS0xPTkbVYhGx+J8NVtjk3xgdHrd+JaSX2MSg+lxR+AkKGrfTiX /r6W5ezrk94fV1pe1bI1nMzYg1+3tLMLdbWOgRTELt7i/5jB2Tg= =3Rjj -----END PGP SIGNATURE-----