-----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/jalu9uZGunHyUIFAmpm8IwACgkQu9uZGunH
yUK8rxAAvMbp+dBi8FqXzq/wT/oDAeoEPn7Tu2/NIc1enLjCmZbWbI4JVpLLjA7f
CgLxi4qgbc7abcuM9cs0uh9b2I/Kg4a9lCwdCo1oLU6qMkrG3/zZgYBph89kOxVI
pwYgpVcfbGbA2cyHaDlXTOzMK2OxtJSIMDA6zaauilQoZ1K2mu0FSVYvQq6HbF+2
zzJGTyHJ5qxBue+nQaQWbufFUFgJJNO9dn6l1a5sjbk+iQG1LusBcXSOF2+GtwxF
QKwbJwEVdzOYVGJsGiyOPCnmwlFY5arfLgnabKnfPyDl5rUYF8IUTNe/XeEAZMQK
i2Q2Zi6nVpjBgkCsrzREA4F7wOKweuhMQ1P3dCpuOQCjGZnMGUma+P8FSuYFD7tZ
ryHmis9SIzdPkNIyPCY1m3e39Z3XgZgOvIWMMdGw2/rczG+PQRJzZyEHFKh0xlQk
WbzsqguZTjMeCGBxaT7zD0XpkVBsPgFXLeTAvvbNqnIjU5cIRmbnTqHqNqtd6kdA
YfYA0H3GtyThcdIlDlWjGxx97OTRw2Hn7yE7P4zt0hSZaNsAKMdQzqnsbAEn/Mvi
9TV7y/KSGBGSgVyCpctkoMOmwcSWundBFnm+m7MnX0KvX5j94pbFD9PaealDNRx+
BB2aQjZJTsFi4Gq2P9CL9M+z+foQecRccS0EGMrhlDjRRuBy9A8=
=PrCK
-----END PGP SIGNATURE-----