-----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/jalu9uZGunHyUIFAmoypHAACgkQu9uZGunH
yULVSRAArYpFw5zn/PGJaFq0VY640UmHN2h1Smeleq+uH0dgsolp+tIwlSb08eCn
x51F9L3qniZ/kKhxxSl81HeaVOmJCrlL3AQHduGqtvGktP2TZc9uCOWLawcKQrAP
/NMEyb+jCJnxvHKWBTMQBmQUwDUa3RCj+PDgK9dhphZXAQihSq1z4Sa4EFW7cgQm
i6dvO2ZSAU6Kc3vpg83dEdXpWylmce96l7JQVDcVDuTJefW3NDYmOJXNBP31X0VR
4J9ilX8R7qnxuPjK8PMY66vvlK46nG6UiaAWMot+LO+MRDX3PDNdtA7TFqEiVRHl
W0kXHf1U1l2IgkaBHESqIRk3QZye3XjdbPWa1B2QLrUzOFvZGndoRcz3nU2KW7C1
PFmTkDt3uk+2U1ZRZCD7WeThmSDQqS6V10uLw/I2HVxJSVCbFpBGfMhd+Tl4/1Wb
Hqc7WxoEmO2Uhb26hznOBFfA9crQUVSTITPACrN5yOyTPbKjdyb7737f/E8EejTh
C6ok76N4lf1ZUCWW/ILJ3JrVMJnwCKUWpVYzxBOqiKfoOJvd8AEKFChVfyw7NXi3
3SqxxhP4Mm+IrOEFGU28IV7IS6wyvSDyPRZtE3FOftRulndyhh1+REpl6s07RYM4
Ar3sxM9dS/+9Y1hIEXH2AE6C6ciwzXA3H7s3RNpYf5slBZQFo9c=
=4H/k
-----END PGP SIGNATURE-----