-----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/jalu9uZGunHyUIFAmpSWbcACgkQu9uZGunH
yUIu7A//aaYunsDNG+NY/TDnnmKv+rHm7h9RIYBFlWVhxOiR4VLbfhPnv/6aVllT
ZLteoTYCk5zWcJcl2X5L5JK14iz5fq/kPvNYL0pbXaAI9DUmJ8vzMLWeFfMaxK5m
D6S5iwiOb655TynoSjfkjKfqyIJdg+pvOCd0286rRcGvaTyQrTusMUZ0aWEizVCI
+FMD/zHPflEvhKnfOODR1IvNU0N69HWzpswzmUq73VcA+BHGB7RGAGA+2HrXrKjm
DqdvmCaU5TRTtAMIb23WWOeOnLzpelWFPMel60Ptd3QFeRLms1V9JhdmDqKSEoud
Me9U133sy97mFRRkZPXFgXadrbAA0HVk0/vyup/VBewznP/5nUwjPrUI3FNzTMXB
yPDpiz/ixAoUBs8bRGXJHwyBbqT2IXoml0THYzil5CM2rm6pT8SSUyZ2zgvEKk5k
xCg4X9nCug1sx3UVJB15BVtW+5ICaTMJFGAQj3PZWf76kD9URgJpVeXaBL6vgJBm
zLxmkG5o47sops+7HDmIWe4lPcde78at/9hKJ8pCTsYuOpIH2/BQaED57OU2Xzos
RL2yZ+pnGH0aV/Nv/3gGXA4bOUjDaSVE++zT5YFuu+3ck+533u5j9QctvvfSJcwn
7ls+TQ/brTHbFl7n5r8hkYaRUdOcGG2NWet52MV9OA+yc7fqJ5g=
=gToO
-----END PGP SIGNATURE-----