-----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/jalu9uZGunHyUIFAmnQQ/oACgkQu9uZGunH
yULU5A//bILikHrvK0UJwvcA/Hj4F4qfv+MORHNmlJ73/EVlElnW6DC4XDojcMt/
T1iI3Qrxivvpj4PHK+MRHzHvrTckHx/6HQnXHqhBN6jzY4HUvAEGMU3hIth9KaCj
yekJC8GDBUld13CMrZ9afAyLMdTnARAPfBPvEpnvm9qprMfadyzo4jSRnfLc+BHK
vZ1veszpaKSoCs6jEa+2JAKe8s1Q39mRQAUtLwjrmX4Cnhv430SZWLQMq4/BQ+45
PKC+q8THtlDRcodiWbdZgQ2nOTYPmciFfHVYggP3lFTKcn4S/N4EgCnj7y+so1aC
elJ0UYZ7tErDc4ZtECrC+fQOKBKk3aPVxINag9RQYJwF6Sp+y4TwArFXHSSdywsB
rLuNI0raoqDl3IQEvouDlBpBSpoWKiF0x5jh58xcFEH/CiaKyyIkE7ou04Ml41LG
kQDQq+o6EDHb00EnrZ1nMYdcIe5ffeJKwwrQv3eXwEfMZUC7+SxraZNPYlKnctqa
cKlDJrpcm9scAjN5OwzjkR7oP8GE1gn5CDe02kY1mCDjX1NpP07ypgBNgItc6Mnn
a//T3rwI0SbXSupU3QykjohYNhdP5prdk0GW2b81/KLUFL8MDy4XaNYXBMyUTdCA
CRmhDa+g+EdBpLQ3udLoiEApkSb6mgRXY4lqvjgEWkdOVPGqtIk=
=Zzx6
-----END PGP SIGNATURE-----