-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmmB1PkACgkQu9uZGunH
yUKQpw/+NzP2wAbfpMMJwCH5qDsnc4j8IqreYhjdSczI5ZUOjhKvwr/F6LoxrayE
n7hfQqmQeEitsFvivQvihWgiI/hDEAR2tfvlkgn0rK6feqA6cTipxMeq2cLT1uf/
043Vfb48ieoJgEwLes6yRPGYc1y0mfkrKTjkO+2LP4Fv8qIREgXEYEfL5FQZl097
2eyOVdR6MXRonEZbxTcbbz0gLcMcZq+n2OQj0Y3dqjL3xz1lpEK1qx3Y7EErWPAk
o3wgRnhVyQEi0mVRcHTtggVUmUnsMBPAB4G5WuURkhFBsKvrof0bz3L3jxK2yvby
XxKAsw7F2wUdBUt/jvHN6IIFsMpnRthCnha4tI2DazA9WQVi3rtf205ivLfDlJJq
La+haAhW6oQvxOleYOOt5sYc8SZd/iQAigZy49Orilq06ssXaeK8p7iU4FEzJqEw
PxLEZpa6h6qkc0l053M+VwmKgcUdx0QN4RrHoTBWtKPBzFclDchiYLTb1DNJmu4U
B6QJOxPpeEjAxynxRoXDCa1AVd71iL+WAVvTv/79w5toKGR5k3gmramgOKI4Im/4
Jz9EGmGZjRMjm7eGnFD6jgo5f/WFJhA+YPaV+3sd0yi3lxyC9BFeUmayfNXK71o7
GxxuD9GDuSVgGvEWF7nroWHcXnVLWh0e0MibxEeDafkWxZdPmK8=
=55M0
-----END PGP SIGNATURE-----