-----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/jalu9uZGunHyUIFAmoyv/sACgkQu9uZGunH
yUK2bRAAulsK7mNMxjZfj7f97G0oSVYdaIhH3T+wdWt5qcLAAKtLqjW5WHUP+jGT
apDnsItxmRwRvtupCHlfYljJwKc6IWmomn820alH52nWP8eLpwSZEezUfF/mo3Gd
zDF1jCb3RZfl2lOSp6Lw8R0ZctHNk443OYdQS/3qqxot2lugfHzgrsqFaDR0puzN
bqF23XQuT3awIIG5w4AUsQsdI4ZeImIzUAzy/IDMZmn5/vLFQcexKK3auqja8b6P
p+VpdV0zwityyytlH1fsGxKfW9ROPHRGMb3KuB7FPMxLrzc0GK9EHMywadUn7O8i
xBMtQrSaeY20IbrtvcaN21eyBVy2YRJaKTZaBa3aE/vpF5Tp4ywJUArFYc1qVO1G
inX7EvibHGhPNnh+keGZMrIKVIGd5i52XB1q4190+pQQBh1RS1JGsMUlIDfVFMPp
ew2CFi012SAYT91MkUdhPs/+VO0GO8YcASAS9NwTb2DASsFmHQbOTMgjF1MtkN8J
zupsK+eSGnABaMt16FFb6keB2kEVNP0Z0zzY7wztDBNrm52Ay3WY6cQwzXzTpNU1
fanJvFPyD4UAs7ofYIrnATXYS37Wsd7phPOf85DX9ZPIYXXMtOflwJ7hsITGBiTL
7xs8xm+SEZ/jQi9LKAjKVIHz/dXT8eHizTzIC1qYvOnMJkV/RWk=
=Ujj7
-----END PGP SIGNATURE-----