-----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/jalu9uZGunHyUIFAmplky8ACgkQu9uZGunH
yUIMPRAAmCT5cEQ/agiZ/bLpwSt6YFVR9ojjToxL7lDSVhkHnWwLjZDMO3noUKXP
tqo9vTwoVCCk+Eg4d6c9iM6xSNt7DHuBGthY1LrHGZdZl07A9/QMeWSBaIznqgp9
YkaUnI+Ia5qjfUZfJoKugpGbiuhkAy+YFxhONtwt1ZO+y3wipYsGa7/hyxhv8mLZ
Wh/5IiswdSoSM3vJgH3TzmHjSD9veP7N0ul2tb9riLt9czsZSyAvgWGaEkktkaou
3RuXSh7VEJtfuEQlmWn0B6wWUBo35NYQlMVRANAGmRswu0zVljY+Zh10iOxigY9N
YIsnRnvDAk4zmP/gtLwiAnsBA3jZqFACeJSNVBEmOgxMg0ZXA7XMHw2u/mvWFhUZ
Qd3awnzkMFf/wYvLlWqoXXBzIEptSvI4Q7XZjiRH+ocW/sAiRZB2DPTrAZW4qIly
J+BCXxH/48RXMEyCpnyjVcPqgdDTo2Bxx8xUZm6t9/DZk3K12kdoqDOH+W3fhcR+
wtOV3aEGiL+eo6S5VrZ1NkbXvtb++acD4klfPPExlTW6fKazCzrK0jhMYLCjEEJa
n3LZLtwF6i77mnFCwK7pZv7j0Sdi5e88a3EFts76P6zW+c8qoV58jrwuy7MDynRE
aMoPC2TPta9m1LonAA9ThQCOwKW20jXV6YSWHrENSJSDa3UsRjM=
=1RL0
-----END PGP SIGNATURE-----