-----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/jalu9uZGunHyUIFAmmd/uAACgkQu9uZGunH
yULA6w/+Nf3efiWKxpEmH+LvO1TuWZMnOOM7bFJJzqLwQEmiaCCz75EVgOiIvLPh
m1tRXWEKwLRqxOxX1IF/SuGSAuMqk9Oev2AkwslAttYeNw7U2edv7crYLg66jUIz
anQplEzyaC2XMQrWtQeY6Kn5wzZe86DURKWO1Y3dRYKlLSJ2sEx4g+qQmQi/mWTr
p4O0/r3xfnx2Pw5BhU9rqpgSFHx1WXJVj6miK68wfpbXKCyQD4I14Cs8TJktgBOd
KLcct0e+B5FrAP3o39hwoZ1CDSCED2iwj3jA318DYSGKpu+A8h864PF+R9zdcJiZ
DzfqoazztF4uVvTIrVUzNnDrrT8pI3QLVaSxmijIxbPgc5m/lKjpyEydPv2y97ve
Atj9FFg58MUN3zTPxcA+ZeZsb0msv1zlz7hblPJECSZcIFW0ZZMvvezSS3Ul0xK9
/pewQs/wQAkPy4g6nLNcM3ssa2NKD9lSgiO6PXcPP3ltnVK62fZvIIF56C+QR05E
Qy8Mu1e7MsFxZDkt3I+x4skposXElsCP+I2/t+XYcdu+6YddVR0VgXS9movluMHn
gdry51L2S5i45wVoC5DNvwzZAXm1Z1/0a4b9ykpHO3x9QQzMdWKOGyz7NoUNpr0C
TfEgwVD0u91IH9pJLy9+Cm75JvQ3maE/PtL+7cFTbbVBVCCqKNc=
=pE1i
-----END PGP SIGNATURE-----