-----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/jalu9uZGunHyUIFAmnk9z0ACgkQu9uZGunH
yUJJ1g//Yvb11YF/m+EaOWP2QHSJc8UgZVvbwvIqeDz1qE0SlAUOu2fotpDM+ty/
p11rSUtKvckaI7TwOQGToIpXIVJH3UuugYmIWqtNLNf9EN1ItQGerSXondndcc9Y
5PLJDaRYWGWah1mbsFNaIoL2nPf/VEQwoqwHMBWT4gBUKswVGzUJ8aRgB63GruLx
Y+IDEPnC/Otq3DpjAm5a+R52YoG74pNWiFLz0ebicqOGmoGfVWCcK/EiG4chzzo8
DoeV8H5cvdNGtKhBl7E4znkxtJDRvQNaE3CtaE5rdz4gVr1ZyouGGVL/c8MUQ60S
HytKa5Vv6+/w/5L9dOfvjyHQYlSzaWkmdvVRP49HwzxIkjzteNKvmky45SyYFRu/
GDDy1gwkRz5+y5/dlC36x0UJY75Ks4j5QYX6dVgyqn+36ZoJbEKrE05eZd8e0teQ
4VA+Yv7uciFGUT1Gg+LDxd6G0tzholEAqIGwcAoMUWlHu8652BdUYNy/x1UdpU5a
VpCT1r9d+m3vLmIZe8alnuhdOkL9TRIQtpPLGDqE+1h58K6L4bPYtijZqlkZ5Yj7
tUOA2ZKq4D803ag1jF/Qja9Zd0hXgI+4teoB0QlwMRmfgIui6H6K/Y7lCtPiLfKv
0VqBeKGMAUOexapGt6hL0Hj7W7EFml4j3xeMTA3StGABQO2t9FI=
=EmDB
-----END PGP SIGNATURE-----