-----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/jalu9uZGunHyUIFAmqMQCQACgkQu9uZGunH
yUI87w/8D1K57dnXDUt9+5RUFj6V+13qVpQr8+mjrY0lZCBgnxugxArVCtTWgzT+
U1mFn5FqvO//h0jJC6qWbG1mpqOm5otNo9AWnJQATbEUa/kHhVhiSUhl0Pehz602
ZP0Y3iCd9Or/8Yq2HZlLZ/guWHsq8PYOgtj0RnM95IsmSwBj9jtT9Gg8FCob9TYv
M3WJ+m3IDdcMXmwjNjL+WiQMCtbXvV0rKFjU6iVBeRhyw2WLI6FZxuNIf61v2GHZ
7KiQK/1YV3QHoT6dNoH2e8CFRmL/fxXGUW1frDUjt57bJrvs2Fjr4lGWhuBiLaSJ
fyzB3Ft++o2/697OP0NNWOzgBB+2XAh+bYh+QA0oJHaJUw/IN4J3Cqja9R07J3gg
VUU31Ph4nw6h0NPCfixvheMkQI/tg4b4l6bqZbTepv2O4BtHqe8gsS/yCNH4OZFo
kYqBrfofbtbuQfVBN0M6/pi3q8leZOEZoWmrxFoj4Nlwg/160JhM63dTr+MZfBpL
ql3ADCMmrwxoVulicUl4LqK/lxl/i+J8X+PMDqmWnSlGPE2dmnvHgAvjpV08cpOu
JSqy7n5VJKDbOYSkf4v5tx5+Oa8PYaxvDGq6iAD5uAQGI79UqZsU3igpU6VFFyFN
GVCZa9+uxUxa0Hgka8y7JSLwedTEfTMs1JTILDWyZcdTFFEQoMU=
=Yozh
-----END PGP SIGNATURE-----