-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmr3VJoACgkQu9uZGunH
yUKFnw/9FKC0M9PIRlMzDnQYQh4gXk2HHd4uTZtT1Aq9YvhlA7eq9zQTgLV56Og7
Gn5fQW7D2560abTfZXCmQikDPZYDf4tqBEPmZaeoZQExrI0JNfRAk+4tXcmgDX52
mvXmk1t7zFEj6GU5EWobDf3v43JOQuYrJ96pZWwvVxBjqkKPOUHbY2ld6UYv3deZ
Hrjb9bbnRcLVIwty2Ag8etF/70a4xCuGWWaxYDfSeQHfMUGujdcIAG2Fe5fwZuk7
rBpffig1bCxKoK/14lUzfMKvRJLTyek9NN2lsjGPqO53u6w66r62QUSIfjJNQOTS
9A+/yC9r2Br1bgPatYb3zpnz3bqY5A5dFmeX5fPCUZd+X6MSeoP62AiXrWDxt0K2
8WshHUcq+kJPGJEwvpjD8TGv3guqupho5j9RyRwW1wjDTys1twEIQY1sc+G+nh5v
CkVoIpxMYSOx4faJczS6v2PWqYGQUKwkqOTSC+BSZuUlgL/N1bABRIdH3pYbkByL
aKKExJ8/rO+Lk/0j2C66/za++WHqyBL5+q9EaScsN3Zl/RhVAUJLl2Y0WWTOF0ft
9EtZUdYNlFY03CloyxrTIY2TfPRVU2g+NIrVGeM3+EBroyFtXQT2Qizli4H/MUce
px/vXoNgQSqAn+Jb0wh7c23zU5Pyna3JAP4A2xgsSlyV3feaCLw=
=1tzX
-----END PGP SIGNATURE-----