-----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/jalu9uZGunHyUIFAmpTs7EACgkQu9uZGunH
yUJbkQ/9HgRWpcLr+egIwuw0/0NoVuC3GKKt79ev+uDURBHA8ZlGe+5JWh8i+EPp
8XkxtT3dP26jHDxp0gjKs/ocGD3p6Zo308naWc3lsJtSWrbrkyBidFYIJeFYy6EA
nHW1z9OJKHFvziZsHXggH7W+Pglmev2JmruLaXJdGvo+9x31+/kaDEScNE1S6QBl
HlqhD3PQH1ckC6fnK3Qyep5E64hRrCC4GaEPo59OkWmoxXfdNGsBh+gz9ivKMNj4
7u8xlJ1rSx4OHcoKRWCD62d04BwvNZ4CU811PDUiN6eTqJhNBWIw8AXfUsr6mT5o
dyL7TCu7kSb8attlm8pa70O/rj5w+HQxJQar5pwR2qykBoEilqKZTk938y/obS8Z
cg1p+n4/9SMgBC547CCzsSiEeHx4LVjiqUJH/feu7D0SdFEmaNLshbWiW7eDksrO
i3cbye6ircAHBY8A6LDWDuvoGdL0vaOzXiYAke8wesCfXn124hpKd5iM+jRQ5g2f
cUorhEIBOlf/Lv6i8aU+E22v2cldatTIxnS/0oQKXDbUUTMfQZUerS4vMwznvXW6
IiyQ90DW4qf1OB6Hjwk4N56Td4svgpcz4HDlDR77zAi91pg/MKd/qhIoUL7jyFmh
F+9wHcnWKevfYzhWIeMfYUcgTwg+6A6pwymty5KvamjPCvgN/Zg=
=07EE
-----END PGP SIGNATURE-----