-----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/jalu9uZGunHyUIFAmpb8LoACgkQu9uZGunH
yULEsw//RbuhQVx7iV7yANB89x7swt1rg0i+w0xs1+GCbTGAsqjn1n9vej8oZ249
Dg9kEjlCyNSvuHrUhdFC3WDflbyuNEADjlg98uog5/cTsJPa+hH6m2DHPCbsMFLu
f6yzdMj56hGGVAfwjuyB+45izfuncPAfdZIqSnr8+ByngFvbbyTosOkZ4Z2IFoGn
XYWGqg6D5D89YoZ8v8Vx0B27WtBXK//8epcOwjgKqbxQHFjhsrOAvrHLGX3CXAAp
KjMfWiS7GCHTAtbqvo1RnFtkMZWndtO01fxU4PiBZPDmnnKcvNDCByJjsyV9gyQf
SiR2MDUTDakKU9ypZypsCvm37pYFmy8IcrVlAhbUbziGePUSWY0a6oOeOsp0Mo8b
Znk2wvlJC2q7efk2NXegtSai7rnL1ny4tAl9f5xlUAUg4I7T3w1z80yWYHecqfuI
FptkPuxXw1fxB6X/sDNHeEqAjcARsmQftwGo4iDe1SfDUxwwSzRVYexxuaImZWNl
cB/1F3x6jtWcLf1Ch7L6O54ovx9L9sz/Geg2lIcNZ7USELK9c+OKu7Dz35nU1hp7
Xru2o8iLKllwCWmcekBOCqY68hNjIeEqApgX9Y8UvJtCi0tCkdSoiWQpJq0Q2iUz
TSOKUgsLLn59erScLLBnzS9PLzWtjOJ0P6nc6xwrvPD1hwLbzN4=
=2i8s
-----END PGP SIGNATURE-----