-----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/jalu9uZGunHyUIFAmm7Lm8ACgkQu9uZGunH
yUKjag/9ETLJ1Y4TmRD4gruglZ1rFRyZPVSyFPd5jvzfP79F5RlTNSPdlzmZOjma
t2uFFYW/tvbiwVvaVwcTHnyy6IDaszWeyqv1NiCTvlUWKvto/BCIRfgxY7ZwBOPQ
OyVrw1DhU2bvRLiIRV7NZWTci9Mg0cJCgO5AsyDYwz623T8O2HEZkdgKg+jA2aAE
LRT+afFErZM/o9gBL0BVOfFSlhPMGdKBMcbAPqUs2gLPXmQbs5yUP34BGNeRrrgZ
7vxKCbQEmKsnsHvR3sGM82ZQAr6dwZ7uM22xAp8H0wJewP7t+5ruHAzrAYEdRS6H
k3+aPRUp4cPmQ9WbCCcX915IRI/6lFoRltdq44meqWl6zT3iPROPYMh4ZYq9/eVi
t+NjZJRwFzG5IHgQcd6LZ6tQPtFN4AA3RB29uNLB38X2UC4PgA6iPAxvCebBqiIa
5qQNbUXNxC/+HQgADA8sKKJAmAIk4hARuS8l1o9r5TDr0D+D68AWxZieXZ/2X+1y
MEFtaZvGFcbvG5S46bO9+rx6ILls8nkhmIC06h5R++p8SUhSbf0T1U5OJtbrGALM
Napaa22Ocmw8PUFM5pa9tBNAlazTT2THTPtb0oNpJ4V+V2eHlAsCPtbCcuUkXFb6
JzeSsFbkPx/zl3m9LEGdvkhH5V6UT6tqhR5VgGfHcm0U6CwSYZE=
=XSbk
-----END PGP SIGNATURE-----