-----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/jalu9uZGunHyUIFAmn0XxEACgkQu9uZGunH
yUIfUg/+IYUzUH4f9WWjhARBO9uaOkENjyMOMYm8ubUqoYePUaGFuD6dfgqYUkOZ
ycqbGwEAvBEVvKqO3sCDFc0lcAlUlghZU05TlKKgodp3to29hsGOqqVcqk2C/th/
/jo4Poz42Ww4kVBmQMCyvkGlYVWEzXXM9JoSpJGoiC6jwrtDbTsuik4RWKDud7jb
RF91oajugqwjvXzCeb6I/WJ+cvtY55a76AS/DJEBpl8r5Udv1QNR+zfp8oChAlGK
60pnUUFLNCaOgRpsqy6RYeXS2DNPNHiN1MeeDQzwTQsxx8hq+JMfr4cBXkVXZYmp
avyra8jD/0dy9NG4QTerApD1ajL7USyKteLuPFSiz1LVB94qCUfgCI604LeafUWq
UEfi8HTen52zv7I3O2SZbcI+bewc+7PqE5eLr33kNU0zsktFDR5XC8Gqt3xeJy0W
cZFCig4oWwqQ2o0BEyk1CrqOzbknF1atPVDI1lkXx0hKD/IFHfr9KJe8Wld+SquS
F5ZRhonxbynW7YZ+JYlkd7/jK6b5RnUyR6k3Tvx46NFnKpu0POqaRfr3kZy3i+bH
Xba0bF6KQJdzlRAzVtWoRg7/AFtwGMjz9pCZ2TB1vPUmfIXGkpPfmCgj2UGHaTB1
C3bTdyE+kc3+/OAojbgjIlmc3Spv44Z4Zn7uo60wcaCWX5Bnvr0=
=8m3f
-----END PGP SIGNATURE-----