-----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/jalu9uZGunHyUIFAmoIfLkACgkQu9uZGunH
yULYyRAAr6GjIhMqBl6oqGpHuJziFr5TYEWcL13M2Dhb79bJuaNjaXWXW+7ymJNH
bthZlwNL3sJjENx+ebGK1efPya9uSPYp69N/QvfRIRbDExQKywWxOj4g177gCyr8
F4DPVOKeU6E+FXmc0q5BxYmyAmfGMpxBz6KgW3kDf8UlgchnLRio4HRIGT4PjIH9
44T8KEAfI/uCOPH953l87QcV0j06V9YTPubqzJWY1y32E92ZExxei7o1eLtizves
1y7DfBsoxKTWWEa/UFkFzOEDFgvTgQghFFtIicEw/0MgShV8Ld1jHxPxeqKpneIL
ECwp7IV1Hy7G0akimL15vevJKcIh14fTBEmi7MHbN2QVuxqIv5aCBIS19eiJCWyg
SsPrcaJAaEN/edgOcU50jq9wLyRVzK0ueKgqX0lpfaPcZTXBqVzEoZyr6GLvSExv
/c+ijEsXRLuX+Tp189XE+gsilvBoq5ejPPhO2HVuLRLvkq1BM9XxTTYFHfPVaVuE
3Ad8bU1umNWMNqaKCkha4IycLlsssNxY0lNc+YQMhVjH1oTEWv3HUVOYj0vdzxLa
Oh9oyVm55FGZHhUQP6mHH7BQE/6eAYXhSClRQrzTSNISX8S4L03aAta4kHFnnp+X
NRRgwwn2XuPyBRwgBdyzIMtWxou+HgBN370k7PzQ1HRgr0fNLt4=
=H+5q
-----END PGP SIGNATURE-----