-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmpWav4ACgkQu9uZGunH
yUJTVhAAuVrTjbCxpH+4hdRM953E2MRN3ErPE/+ggmfR9Blmp6RFDruKq/PBTylJ
8isHa7g1B9wVpPVjKrawR6AVyCEcOLURm9MeSwI+oeY4J/kpJz8W5OPzQCX+8Z8K
7wX5thFPS6q7Nwzb5Q4464AbkAm66GhmbOzoyK0cPSFSdL/R02UqTstVTEZ3wvOE
m5dRtLr9C5oSwoiEUPBHXP375MIA7Jc8DmUu9SiK89UJJQiK8u9OKfjp5PvSaIyW
tV+OGYMs53mIOOsN/YSfniknKCbrIqTa2b+2/8n0PiDu5PzHLhGfRikLCKRSdk/e
dIP4mbzjmmfty1AHI1t5zqKbswQf6K0gkg6pZ/5BxHy9ST+1q/6Bz7l92rosHiP1
WQsxvQjUNQejEWyUmvOanDOmaIvrlw4gUO8a6CD+dGC2IKrNoTochKEIw8n+2ApF
44pMpmAK6EjK8+v/CPibh1DfDuFGPw4ULuXWMRP+14PKJE0h90Q/MWntGm1sVulh
TiTVj0KhL24vNNccd2nPZD8GO1oBqpTArnV8IrNhLg6pxJ0I65kajOllshetwP04
N70faLVrglLSjtX5I+Pix3hmsm7UJXMBCMeOh4XzB507yJCY7pYvVb0rZ7jZvfy9
ECf7fsNz0DNJhRvlpprD2SRmFONUsfjSa5FvKTddShf0VAJaFlM=
=WJ3C
-----END PGP SIGNATURE-----