-----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/jalu9uZGunHyUIFAmoFbawACgkQu9uZGunH
yUKH0Q/+OmLwOKdaC9OU1mFg0HlqtuBAu6L1KIqD/GER7g+Rhu8Lr0DCuFZb9zeV
uxpornZD8HtpZ971NbfnH0xuAe7yfxt9ZQc7n1lw6pipontCTCfymvKpdc4XQSSK
Y/qYJKSFHUIK3IcWpYI7ih/5ynVsfkwhU2TYf2q9obIhbrwsvjUngGZOKEdXrvTc
jkJihToXdSkCJtZEqHSW11pZLk5+9juf/BvQHSUB/N27HvNw4E2ecfQJV6iOHRzn
hMnrxo/yrGPESr3p1hCLkexK/57vApmUeB3yEDlYTWBF8yYX6/+LqHrGCpJL9tOJ
mx1YxtUjOJkzbl7vxrDAB5xTlCrdC5PwJYHP8CjuEMEid7+Rmm6cQyxtAmRsXvr9
mAjjaXdTAzNi/qv2YMpsaGyB4OiQAV1CTRLNYXC7TeIw4NOMfsutShoVDE/NEMYl
K30eponiwmiEIo3JINEf9S7yPINTYIbPs7JSkV6XYdH1ssU0spLKhoeYEjzvPhXw
jjtd+k9Q709oOh65bgtit7K6SJpEXaeBFxE4PaFRANcdKFhLmAGRT7opwcA02pl+
uOB3btoCPSVxpYBgIkvyOT2WfHVYulq5GzdwgBidqVZhF2IsHvx9DdiXuhiWj4Cw
uk+JPW/7gPzY0niC0DkwLn4pd2E+cMOl1lvksRfYQoH7XuPENlY=
=MjD8
-----END PGP SIGNATURE-----