-----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/jalu9uZGunHyUIFAmqBQLUACgkQu9uZGunH
yUKxGA/5AZ543botAvXOIILZN0oKBO2cKfFsT3oUB4/7vNH2KisF/DqZRqbnCzpm
kCaeiga+1qCJNpRulUzVAKBrBJqX6s34M3RdDjT1uiA24qXzX/3T6woaYpicTF+O
z7MBlZRwmX5zPeVTDtlILhxgyVjCxCPc2oC19JMY5HtAlIGEJyfr/Jf5TOCs+UU2
UBPOXaIYjCVJCwfqVu6MTC3+DC5TnIvP71SHBC+MwRJScTyjMDVWwVPYpYedwv7T
L3KyxXrBfxSJCDgc5Gp52337yLgfYdeVzCT6EzbomCRnHBpdnjGBcwJnIck8rZq9
Mkrg468lWNMT9q2NizjZTKtZeOhKVoDSugp8faP0UQfMBH5GvS+NDDScRsIHLJwY
rxOn9pDnm5xw0ZsypK8OtUnOx9H/v/Auj2Rxv4Hk2DDRFLrDtCEtaByqShK4Cmt9
A7F8VgaStGjnf23pFkPgDSWa+3IKdt1ZfetvuRHUeeE5sYLohzPPTQNljmdadjRC
X4SLvRQenBuuZqZRmpzAr8yv4uUuQgcmCQEd8PfKiliUCezeqOnqCK5SJ0xT/1GU
KXm7N3gQ1sHY28Igua6GQRKsMu9XmQJ51okjjhP0r684PPzj+6Ru680tAvwoqYcj
NLIYDCJYJ2nojYpMUEM877bMgaug8/9ySovY/MjcqQEsagjwGSM=
=NWAw
-----END PGP SIGNATURE-----