-----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/jalu9uZGunHyUIFAmmgAYUACgkQu9uZGunH
yULGew/8DEXxNJPwAIWYmHQqA4HJ2zbRpLhfYJvoc/jzIx1kejKLCTtYczjWr7zP
wAxpwQw05yqh1K6A2aWB9wksR1tkTA1/4wUB6epGpqrR/IVNtb8KE+h1fXGQ9W6/
71OfWVu2op1fg8VwXaFng2Sn3Pv+VZqPzQ35SHdyikF/tLus8UIa/cm1/LDhHeOr
KySSzulX0cu3FwuFkfkmml0LvSzU6eKQQRyjRyM9ROdQ7X1D/d903GgFjg5yHsVs
DIK3QhMMCdvBC47eytIy5UK+PXU8gGn3M5tyJArFKfcDR5PP5OcLYhRs3lk/IJjS
JXxaS/rjiZ9noH7k+Bam3LWtAG6QhgTt65KkruCidVO4wnHUWR0XKFabq+9UXdtt
C4+Lybl9g8zZGr9RTXqMmpDQyoRaRN8DI2YE157yOXB58RDPNmBH+sOw5rcXHM48
FWGKL3Q3Av8FmXKM8BQdV+Qq6Ye96k3yQX0O4iWHhG7/mZdsm7mXsGXSh8Wl3dF8
kF/HY83PsAYwXl842Kz9wdDamFDRENqVCY1xPtp8hDDYHALDuPgRGxZ9wm7+8VkY
fiD9cLZ1BVaipleAe61JV/DauInWtZeAIT3HHGknFMvxvB50OoMQiLeYqdj8t01n
62ZEBep3tXnyx8z4C90P2Jd22jbFHHaSwvUNwxls3GRBM8E1EpM=
=4DT4
-----END PGP SIGNATURE-----