-----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/jalu9uZGunHyUIFAmmJVEEACgkQu9uZGunH
yUJC3RAAoXbyqW/PPCUClMnsGhOZRQt+4a9MZIu6AVRMIDdwq6XPswkurZxDHeqe
lAATfSh2VuiAr4ee7BUq5o/Rm6Fc35goQx4wJ7nl4kY7De36MHliD092J6hUfkuk
4OTIpuHNQzAdiswJlJKEYN34kkwku9NEyYRRbOlKehVqH3Jxjg2ymUBCBEcsJgl1
P3oVTuXU6vf9x2HfpkwO+Ew/IFBzglBRDaALg9Oj69z+mlyRCAvo/xmwNyFsoSXA
AMWJCcGFDhM97ys2eWX4wfAcsjFIQU7J99HvpDCf9TuKqWd8e/Y0Ts0T19a5OQIJ
oiTknXQa3t/O0SZfmswRNa2g70fghHFjjLk3aeUwSp5ZN1pyaAX52HaCRlOyeXPb
47MvaGztGueBNo4Pr8j4MocN4aRwmHPXtOC/I4DpE1tevpsafAi2lTG63SmNjRiF
wAsW17dOO8sm794tjU/3XWXsq2lE6efyaJkcr1QK329NBBwrfbsOR6+WyfWy8wMM
C/eGZbnBZFjdt9cKRemlRdXUQNNRA13r0C+LZH6JZaGZfvkAceL307QHd8lTOVR8
QY6PLXjeZyxAa9o8QLkdKe/gtlmmUPQ6jLRGt34/lT8WnSZl6qQvS6dJ7EYwcPL4
wbn3nGcjmJyXZ3U3lDgEdBet2GHDUCd5Gnr8DNY4QRczpIZk9Uk=
=pSHM
-----END PGP SIGNATURE-----