-----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/jalu9uZGunHyUIFAmqCmsQACgkQu9uZGunH
yUILeRAAhHXXOJhpljm5auqnjvcSqTFKqgnkkkFWL6lY5O/oM/pRzzLNZatbn4NR
o7d+ch2wKKVECn7NHZz00Jc4R3Oi45bWwmtV+MDOCgWvPhd0XeEnOs/F2VbMKaT/
Z3MY+iKL6lwv4oNbZvj6ny43AnkCiVj2kpsy2sFHvyaZZC2Z1pGkP0LQ4WCLu1AX
Cnkycb1zCP21YO8pSNJewsLQAQb2LZGhokjAolxg6LBtxYZqH9KnciFcy3Bz7loh
tDmXWZ7lZ4R0ZR1XAmIM9BTvlJIJx2GQWhMAXXpsdTdYI9gaglyfwx11jRL8PfAF
szZMa9YSTrEoKzL8BNXKFrrGyHgBNK0u/ipwfRYrAO7RHpo2wWbTt38MirvnR2Hu
82vNjQgxQ4fHGvT28FiyJHqsiAbk4CbEe6qXOvOLL7ouiC53rGIS3QSeUJjTGEJD
b70BnsS+Tui1S+HztlEmPSOBCwgxzKX7Y6ukKssYSXhVRvCbBwbai0b0SvmbJYFw
wewonek+5G1QwRJwq3VDDlODZQkVnE9MFlxvjoZYarA7JR2imYpAXqzuuF87CEYD
DkOvN2ng6z0MnIP1ilnqjfrjOdzo/LqxFt1UMdRdKGV4gI+EsBWVGE9O8F9qhrDL
cVLQHRXmhUqTWhMw2YucDzY0A559nzocpp+cdSsn6GSNesPFLvY=
=somn
-----END PGP SIGNATURE-----