-----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/jalu9uZGunHyUIFAmoD7jsACgkQu9uZGunH
yULWORAAjIYQNtvmbvs6rhTf0W6JALtXgPYWcDVrfEDHc0WIypgU0EVmpg/wMQC7
V3fi8k91heiRKdIi+WLu9cAySs7/iMsj3fR9wCUYtNL9qN79r/8TEmslcnGxgULU
kZYICibV26ZAZV86+XTavuf2yI2bljj+C7ShNednQ/lEYxLKA9dJNK0E/MZuDr9J
M+AKIAuNUCywkWGyeYTYbYpgR/dO7Sf/unqq1myBHqbjKRNNgIu/+lXQAzFwMfLN
zJxuFHm0+Wkbn9Il9Kpb14bGAKzBNykead68FNZ4wyOZnYuhKoKm5xtAaz3XwwwG
B2GK7umJ1ePeN4WCIVvUtR8r2SoQfDBGf7BH4yBtMvsl12nGIZgiHsbXekFD/ids
JwiAfcCmoJlgW9iiarT0HiRsWgZ22oS1SObWRYreaZ9ZMLWNe1EAYZyILTpQ2KIy
anE7HbD6+gvv9POFoFXqJyf+ZaCj82DanSOs5/fOiXIL9isGlCPlkCBzZNsisT++
7nja5vo9McMP+Bsb1snXaTMukiZ8Q6sB3CbBnjlMKBIbFnV/tkcRj6hkjWI+b2be
QIyzkh/u3uwdetUbyhQsb9qf5bdmDKj2Ly/WAfAmBLOblZXBVYnVUgVhhgv/ZXFv
7MNr7wy+4tVsPnL8dw296nso038JaIfeJuEXcYtw6QejOr3Ny8s=
=CxMY
-----END PGP SIGNATURE-----