-----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/jalu9uZGunHyUIFAmp3ZwAACgkQu9uZGunH
yUIWlw//Xvr4OJTc9ibXqb6QUWXEA3zA4mU6zHogjpZwU6Qzv+V7Ht97MZF747o6
HKjGellFBoy21fCE3hwrAw0qt+Tvi0e/6OVftGiRMZNXbPstuylcooS6dmWZU7tG
PP4+I9KXGz8vLZ3DtH7K/6fL50MjknUC2RJ7RebimL6wwMMxwKiqQEJVcLZ+VKQi
arZMrCIsQQ0kgtxFEs/LPeff7yHEaNACd2Qgk9FDi8ykui3POXHB3zxTfXUuSEKq
fy42XOfkmoH6SRihbyw06bdbr4bXEqdZ3NkPXydnz6ya6CjQauz1uoj9q/i/0pbP
2Xw0Rc3TczC3eQ3yNxVcyTi5/IV80WG3c/fowI70MNm5GPL7F9EFN9YMbSFGmPOZ
AyFDkDvmxlQymPmE/T1cyLypc0Y1QdGJrd0JQhtA5nnzeswk45gjEp83mXMjeO/g
mAqCnPjZ44D3EYc6RHw/ym4miXh/seU0V7GJqBF0MQItKZS9K+Xw0KK1Sa0Vo4bK
BC8P+xAUTjGRDw3jnBR/Q+NAmM1pp2Ss/QMSAUUrfUiT1hZtVCG7gv4KLWsq7ZB3
jHIpM84SmgDzbPIEev+cb8hKiuDV9SS20vq06WaAIgUP16pAwSw5vzoTIhC9FS1F
mvp0PmzT9sn6BGTdjXhMob2PfOtya6/c0ZY/vdpQBf1uFWBpJWc=
=sgKa
-----END PGP SIGNATURE-----