-----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/jalu9uZGunHyUIFAmpQ+zcACgkQu9uZGunH
yUKHCw//f2PfrS4EBxHXE2H3PsmyAOGj0NYZdSHWD7BbO1fOz7Tdl7gfarY+mQG9
tddP9XmGg8LtGD+jihJrXzI68Hpy0gWhY1B2OHLACOuz8ztbvyJo33R0MZ7PA/Vm
mOyBMv61Z+9Qcw9MeU2KwgeHqB7zsRt5tBY7kamQgQmTgtlYhZlULN1NI1xg4cvm
6MBwJgP9tad2NXpfBiiid+sTAoH2CoewtJlG+ALg+qg9LHOQ26LEvdeUj1tlHrON
iv6tbhzzCLpUgyR04djK4URUDdzu5xjOSolD937uCXilKx5dbp3F1y5NJKAKdvkF
ywv5xKD62zMobb7vX8DSlbKj+dDnNJsC7VMYWVwQm9LNb9Eu5D3ndlfKZHi1HnUP
tQAHLSGR7X8T1KJ2ovzjeqnj6NtqGvASbcOLFSrn8eViKeiayLJsUEubAWvxW1Ng
FD710SC41yM2feKWIE+M5NyYKdA8+SUVmrXjU/f/oPsCXNl7++jeM1ysz0vcSFnv
tamIHWSF/q8lNH7VZEaY3VAOXNFzEUEGwPv1aGDfCGd50/4kq1ouKKLE7WmA7y8K
ER/PY+D43160nlOvAZiq1ZMfAHKcXmwIUaZQxgAXym4QIMgynqQdil5wVsd4D/+y
aYnQobNUuBVX2HhVPbS1jDSUIE1fYOrT6yMfHtklfj6b51AIPnQ=
=DLg/
-----END PGP SIGNATURE-----