-----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/jalu9uZGunHyUIFAmmm1IYACgkQu9uZGunH
yUJpFg/+LGCiEJtHBEJgONQabWCLAuDvUntKftVmbXJGP9DM/m0G6fiAtFn/oLwn
Qhkm4fSsOV/URdU25OtXEE2ovfdksvXJ73JWmJGRn9wDx3ymalWAMQRP2bABClj8
TpWaMPJGuaZYRpYOnmisoQzqYP1Bbb1oQ+oyAd70A8qiUFzKc4W8UmlhisD4WW9s
gG0Vm/wIRUjdK5kaq2Xzh+ytuTeEBFEDBiMKZNG+rsZyvgBANxo2e8GBEOe7Kyjf
JDhOYLpmg88khZmz74x3Lr3/Ya5hTW8w/PF5Lg23nU7KyElKR1S5pLy8pIwwTIgu
RO5ne7M6KrKzKcHr0rr3BGOx/52jM7hj0VPplGOkPkuEAV9decZ2u3yv86YUIT9o
QgYEydXhA0FslVR0Bxph2aLQXtna5jwTh3W6PV++wQtIjd8h9+NmrM7S6q4muKjX
Ex/g9w++5DmdRV0V5H2w/Ku665nrWkMz+YbNOf8/nntnuh3py7Y25CxIfb23+s+O
Z9y4qoMBmbYYpaVbIO2TXmbu83LD6Mx2Qp5IWXv4ShK+SGxuMg8G6hMajIVThM9r
ZW4LU/B5u2/WfWZS3AEp8twnf8XEHbm2LBfBiymhUOfTWzbgEhhYRXgK8E9/xytg
n80AU/OlQmxuQ7wHSKo5jksMwumcWbOYKMYhcV7Q2gF5zkjHK7M=
=UqGx
-----END PGP SIGNATURE-----