-----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/jalu9uZGunHyUIFAmpdU94ACgkQu9uZGunH
yUIjGxAAqZ9u9oU46ud0yYsb9mCsOWNk04vc1bhn7wUwB332/BV4h+tdAva6Jrqg
iaJWGqlksq3reqB/uL8vmreZBvIkjc4pIl+L5lNeFaxInGbPBdYJsTjbCcP1HM2W
BlcfiIg1ksrWHwmD7hbZ0B5hiI3gNNm+bkXASy0gdWQZoe6RUCA6UF5YhsP1LhL0
aKI/SArvT9ep+OLFovhoPQ1LrlWg49bPZiN+PdHLNmbAJFf0mE0Jw9FnBxu52yd0
E+bCmZ2u7LE9uBTr2Pt/PEvGawyBZTUTmDG0mZP9bpIF3KJl9yuvL0JGQZnmIE7Q
EjYsOHrjvbR2AwO1juCTUnaiUhf+F5lIaOoZ0hjFKzgE+yAMbVcDvcjDSh8Yfdmn
FMF4BP8ijdQ/GIVkBgHNackD5V0rejX08Nz9gV/JnYGNnjcRoSHoKvtwhboMpKjD
J8baC0YbPel6M26H1tttt5RfMB5Uq46r7hvzSV97Ch/TmWGHztxQYDr9AlkfdXGP
UNkiu0FyhjZzaDOa7LE9ej+Wt72cTKLBxAS+wOw1Yp/Wca7aJLCWaCD2NK1CFBk5
DrOUgGWhw5nHgVgjrfWqqMJFvGedePjTVlntzaahcPqQtk9ATbI+b/3ELc99mR3E
J5uYODa6bxxHFa7WaGaxIXRX9ole1Qw0WAiiOAolqV719W7kPEg=
=ig7m
-----END PGP SIGNATURE-----