-----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/jalu9uZGunHyUIFAmpsWYoACgkQu9uZGunH
yUKZeRAAk91kxfei8OhfsvxRespq5H9Gv4Rj+ak7gIUOy4eSBGDSMRm/bHSBmHjg
tf7kiqkRtStHZxCAVJQHo0z2ZtJWZxCgrBV4DAPPNArP7E+G8L7e1XfEo1hCv0d+
IigEgxlzjoJdtYmy0BrY6B9Uc335ZIbGJo2Ul5WGJS2pWxHMMdBpaStAuQBkZgqE
oipni0WQq4+JBXrVaE60EyCFjB3rED6DNdHpmdfJ+dGAczFZc7zgcHgBrG4AuxlK
kexEaGJsShhf9KqJf8KhtJjXIoSL4hDV3C+cxtOLi92f56f9yNlX9r2JpMBdycDk
n6KKX6z4pYTl6WNJmJ0xe1778VjqF2k1C3XraCbFGmu2QIcGYluI+749oaM5I/V4
bbfyOUZ7x15UeMK9y5rF5/xJ1sq8cTcXnTMt8jptlXEgCEqu1UZRKWUePf69u/QF
t9jDFz30zNhEGkXd1/Kt0hbQgXVOgYUnFsuvRl0pxCNvBlR005Y+MfjEZYG4ycLs
Vmam7JMB0YHwKNj0VlL7FkLZO99f9Vh4Yuqvonxu9p3q4FHInY0GCikSTJZq8no4
IHuVH0z3JxWbYJ4ueMFSnkvZume5nnl9cmmwnVebaPUNWPyGqqLlx/0jsrl5pzby
6GkcSNz38UHSATpB6dfBkcHwuaTx8L7WB4HxMilEkWIlEdBa5q4=
=WaaH
-----END PGP SIGNATURE-----