-----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/jalu9uZGunHyUIFAmo5pcsACgkQu9uZGunH
yUKuRg//bbCkHE51loCxGa2ol+uuytYgDpiu9KX+9GGAEYc3VIjBCUgLL3C/PvID
x78P0Ga3sL+pTNBNn8fgbmEJrrhohiRW1DF20me0+DPmPvF6RN/x5itU/MLHH+hd
EVW110pao0u/1Zu9KseGoksm5x9kVzrGs+Ut4ZTXrRXD7hppFWw8/HW895R+jy4g
eyWAiXWQu7Gi2E7JPC14LRIEGkd6GDP0ljKWnH6JrGMnvPB4uh06EtK3KWJaAOTz
q79h5olKlNKZPlGK3Mfmhc4f/agyuEtIAfftFhZfxINaG98kqCNvDrS/L02qSfCL
mkGeDTOiIoyeGkzeZ+zdkvVb6MefZhqI4EAB6TWmHE0I1g8vlTrM0G5ytsAny4Qg
hfE75qeRGT0VoISkaMz4/gkHvqqFAxlDqfZz9jb7vIDsTs0dzWNW54hpKTbDjPJh
NC3P/1Q8Ux9fcyC8xNmkxPNDRK3bYT33TV938NWAiygwG1xaf0u01ZxecWi3vmtD
9pt2BTZGoij76z9ko+67yTM9UlncNwFDDEoBV4Bb28RzJxYspqTTeiAlXtGYtffY
SghDtljq3lD7C8e0/pSCN5T0hFzQ1qCLN+tWsZ0ptJpeihb/kko32RtySwu27biR
h6m0qvJgS2J5n2JsDvE/SYS8VekXKhJ0AByEYPb8lkPhYMfFDWU=
=6L/9
-----END PGP SIGNATURE-----