-----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/jalu9uZGunHyUIFAmmlcskACgkQu9uZGunH
yUI9zg/+Ml98xjj0HjEqpUj2SH/5s3GDTo+Jz0xz/K7S/GML6EySdDs1ldkjzxy5
fWNHNjOHDUzvdTknc4b4JHTg9F3KYXnNPmJr3hUX96Tqpn9y/draKXQjEx+ruUpe
GxSWldMW4HM7Slv8L1hZojaNa+FN/7VfIMOorRxLet8BerzZlsr8SUcTVgmFDtTP
ovuec0FkCqKzGeTro7bn7F4blzJ8/t/HzXaujMOnxSDzDpRXddaPbgXMd0+/hFf5
lEHwAjvb4LIWleJeMJjcZE+PRZIGvp13DppPlOauu2QCitdG/ShwX+ibuvrZI2Gx
A4Sa5X7pORoNgMMC2mTbKT1auOK24Bkq4G8wDviQOf5IlvSI6E0KFNQxJ33pjz6Z
DhNW3DXlQhkf7q/9qJcCiMvyoxb+8X2/iECIqWptB2pS6ZkjGoZWhVjxJmeqpjxm
TyyzgANhCtw94GeEEGtI3uEwu+sm4X4J9fJd/Fode/dIzEaqMC/tSkc0CZswCgtm
Dpr+QRO389JfyM5EhZRkZP7zYtPNRzOH4BjOI/BzP/lbtMWG0mIYgU71KMv1uizs
Sl3eoe7GiPuAvbtrQStNFh3guDrHYGXX3QkOa0d79OxKjDGfUVX562dwWpn6wWb5
nhG2JrKH9V+jUJiLxBpby4pO/LgJfDSLPv0RYK8+MbBmN0SlhJI=
=95CO
-----END PGP SIGNATURE-----