-----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/jalu9uZGunHyUIFAmpgKqEACgkQu9uZGunH
yUIMBRAArgejKfkw6ND09iB2ytPyQKacJPKoFwbRUdfnZ+80ODM68J2r9ltuv0RN
zOv6NlkvbrU7iYlQAgM8giO5fqd8lfe/iSxd6m2irva4309MlryJLjG8LYBNkllR
lsuViuPArGfYL3g+oKOd935WhKvmc/ahYCB5zhD6x0A0VwsSQrax+aALFG/HqW4P
fkkBLjQWnrEZWBRU/DVGaG8k/ubPSqHeIv1ijZMnpFK1u3gL2V2X71ABdAlAkPAi
jVY2BkSY6Bt06eKR6oWgZ74VoGfEkQJuMMfG1kobmKmx/dYKiKzS9NN5hHwbKlvj
vL2tif7yi3J1GsT24El9VX6cosVJGcPQid5ZxUPe14AhFOwdSShJoVHsFhyynx6Q
1PCmfnV3ktpTKEn65thGax7cxWU4/DIcVVI+jQdWdpqXJmaSqDhhwl6y2wXvJIHS
2XR5UfR6qTzEApATBzolb0cC1bYBGdXz7zbnO35b4X9QqxH5xqoDjYg6d52BmDrG
Yhb+Vl96d9TGpJ0PZ5O9D49cu2KzMnhd1iDNI04UaqxrPmfHfBHd9fA3vHSAJG6r
wV5d35Y90hPxYIPnMaoPIgg+O0FJdVug/dLgliqQt0mgq2LQ9bISy2qsAdcvUbd8
bdICtP1aDXfw8EIQqCzY5AUgMuL7iYDjQ3KXaUaA5kt1+6Fy1Mw=
=qwsy
-----END PGP SIGNATURE-----