-----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/jalu9uZGunHyUIFAmnJzXEACgkQu9uZGunH
yUJRXg/+MkWSdcj+ddAbs/wOOl0O147aLFz7GqBEIPZ+QMvb9Wa4wYs8B4R8lEpP
PLtBO0ooH4Ehk7kUfZ7VmweiN/BCbACATHyHSZ5UZUIQhyjD6MgDCr4AJSkvkYNI
sBg8CJ1hQY6CVZxs6glY1bmkNnlAyFazn/pRK9KDWINbcY4YuqlgTpU7K95hYRJb
gjYbdKYoqmvPhS393L1OukZ3TgLtBWPmVefFmPSaUxVNazDcfZSgofVe7gDy+Ria
dHRvuwBTiv0GImZyZ6t8zFyoZQkboeIspVVe2b4JK39pPRLAsXJ8gDY1D+trDArh
EzvOiONffduhJYbYKEnnwSxqIqU9SSKoBDAD+OsRch7j4kZQCA546uKLaVTbDxxT
GAx/i+5CUyejP6hp4/wBAhi0OaGs/wBttTiV7P5NB9zYPBmFgZEosY/485x+v26s
umIEcxBwjM587JFv5tSrP/iDWXR3rTf56W+v3lkefrYx1PWTL35PkQoGBMjPaqW3
/bUI9/pt+tbUK0Y6oWhO/Wre4actvxt6k9OJXH+emdQrTyYwoVDvToJX//Q/JQxb
xzP4wzaZwvNUW0/KU9ISwQWbNpaWn3uFG8WM4OwamhZn7dOQ8zzoPAe4H2nBM2co
mHtTwt6+eICOPIbLcygAIDmCIoeKFrY9e11I0cXsdIiMQV1O8n8=
=5gqR
-----END PGP SIGNATURE-----