-----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/jalu9uZGunHyUIFAmnsqIMACgkQu9uZGunH
yULKLw//fNBbwLuJttkHZUlU8FifrAT6B4+UBrRka5M/KAE4JvE2Lvfsbj0fPvxV
+oM6ML+5CljfFAUhSKih0lAivG5dG2AAL2YyzdATfv1BTmhU46+zxZkHCb++xQ+s
uOV4qY6HIaiTZtayhahfvs+u/KuNpQpW7o1wtQ9+7X/x6x8VDX9KtIyOp0v7RyK/
JdU41odzCvVUFGQ+8SZ4mSR4zFw4bd1Ek1A0KWFjdnHO9GHpHKM/tsj+y7BuEtmK
jrrsopt2bgWlUBiGsbO5+GXQ1/nimZc3kg8FbLLjDIq9tsfrYeSnQwB57gpbgKhY
Ydtiz1Oaj6hj6tLhKFaPAMc6H8dje9OiXXxKZjtb8+fdfWDSSV2L0dZIaIgiGb52
866ZHSqXRLeBh3KsnMUtDV8qAm+Qb8RTsj1VuUhkgfpfT7X+xll8Bv9bD17xpRV2
+r1MtGhXRKj5pmMnbdrpjNTmL0/RfMYIa7qcMUSQVrpK+ugTy1bV20IwXAs1XfTk
6c7w4odNDgtjrETYs1UQOpOFCmbvap/wht+0GvBYz86v3Rcrnq8nDUry851nxIVe
1sTVQ7PafdpCFegvxJkI8GSyE8TvcDusJBgVPt1Ma/1nsnREsF7QqQDmM+0oMw0Z
h06Sb/oT61NDUd1rRDgmrp9b3tQeY77tslvWmMz5HR5PDRkxFTI=
=AwEU
-----END PGP SIGNATURE-----