-----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/jalu9uZGunHyUIFAmqO7PEACgkQu9uZGunH
yUJU5Q/7BrzW0tvOXQ2fsyrXptMynMghQ5sCRFo2ckwXF65lRCXRKK8AJSY1sJcv
eMJGL/WAvK/FoTpxXWESMscaF5dPxgJ7gdbyiSL+XoEeyxYYAcLc7NxO8ydbueze
y/ijjE/Urg2YK0u8Bc1Ja9Hza3iFZNBc8lW1Sg36gQNXWEypnrvzbBFDeBRvkYQu
PaCbzOBiVtNXunAC1PJH0CNlZz++THr7TCfVoEdpkiaohHYZN4wAmanVpyTUuVCu
Xyko0Lo1qblZlff7GHVpb/v8sxyrk1tT/VPHFA72D+fZDmkTAt8zQkF5t69BFaR7
zIDsIxVJgVMDPmeDYoRQ+1srMRAqOmJnXtDV+btzGhWBIrteo82fURj9MTpsw4QR
BdC/wPDis7iOzbmZ3XQ06P7zGiiX5I9jp+I18JoxkWbLy2loBU3OYP3pYBCqYrlv
VE65QWPq7cZuGja5oacqra51T3uxWp049ueg5vQ1xySq8dTlf/XQocEWfXmoez+7
9lGuiMXt85r+K0FEEgx5jBfWblgCHFRtJnOaOy4M60emVJbRq9ieWBUFCBF6wUVY
G8sPn0olA/VfLxeqDegDrp81Qf6XnGgHArzVszYGzJj0X8GU9TcUSy5vm/Q611QA
1Sf56XzBeh/FHsVpqc3JnR6P+qhGHLGAPjKxEGfg92Vmk53fUsI=
=kx3b
-----END PGP SIGNATURE-----