-----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/jalu9uZGunHyUIFAmmyj6gACgkQu9uZGunH
yUKnAw//YRTKL/CJG+xCWw+i0ArR+z9bb+qRS8ZH34qZZHGmsrsLrlD8nU1oSYVd
vuMpKf40iX80E3oV6dNQJifXtUbRhi6nqYTV5N0+V2MCQe+3upWKIBlxyD1Y/AcZ
rBuSDBdNnOvoqLBZAtoYTT0cowwR7OQ28uKwDFrp8HhC0X8YyzvVTXajkvfkViyq
HUrVQFXXtoMh1w4hRPjZfULrPoFIZr0TPPC6HWBJlVXfGe9vZ9LFE6x3mOsG7oQ1
n6Pqdt4hH+P5thuK9riJIrqQ2k7DTLowmAoUVdi2ZjVRnDiyG2Yvr9uGbBj6sf07
UozXcoSO4rnFdhJJDrzWSPTvobAETn4aLeDp7AGhmernSqQgHHNDxwu2F4gyPbNr
ggXqhyUgyxrYm3fSO+s20xdqTfcP2+/N7V7y7T9sUg21FTim/L9IAmaHq3dNIVQK
7GUTtZ8arM84Ya6kT60sZYDt5TwwR+0yBhWZUdZY9XcPHEaG2DGBcMoOhlCTptun
VN5yARHw/Cnm0tvs9Fj1xBHf5OSzus8Qz/qEbloLsA3yqsDZeMvm1ACPRupt6z9l
qV5ZseCeqOhAKCoBizy2pUe7NfaG+l8S/PHsRxhWXxWO/Ov5j+zn2IG3so/+kB0D
yNY3M8VSqQacSGNA3txstWStn4FECxQITUNrWHs6hAnDIS2mOTc=
=qkDW
-----END PGP SIGNATURE-----