-----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/jalu9uZGunHyUIFAmr19T4ACgkQu9uZGunH
yUJNzg//Rq4I6sfX/rB9WtWd19+I0u7dW9jhUvdZbPE5c43T2/Z09F2IUtRH2+xT
EgK8ABDrEg/CTyEH3iFDsltemM5NXjIB1U24+sf97PMMwCSPCnGfJ2MECHR37nmF
xGxg2MR49FHNc64Rb2GPndOO7wbLPRMvEVT/GnMQMXdKhhfiebHlg9x5EuYpZmBc
Ig5UHBLCXiU8D4PJX0d8QsbbTcNAaqjm0blGhFMCGny7c7fhHxoXVjDanWTrT7Jm
gsnaOfm/nBZHAOt42a95Yj2p9CjEy94nBUBdCcvMF19q2x1w06GLD5mU44dr13YK
tnqau5I7yQasYYhAfhuG6gIdb7+vZ9OBEeNO19MuUxsusJj9dp3aPUJasGk+G9ZX
PNtMLkCJTJ7ylhJgbT6PmwVdMjs0o4uaqIVnkoWGaIMgc2buJYxLtwclYXSsU4DF
BnnZXhbGGFUlsYE0AVvLQstI/dFaZCnmDGJRND026yQY59B2g8SNwIMwPfpyoZlS
IQRagskyyZJ4E2dnZ4RLmqOC2V7bQbUQBGzVCQpRAoV9BhAZ20rwoMc65ADUQMun
vxwap6gmcBJ0osE3juMc8y9c/HMYKqR30H23MPr8Szl5vT7RHr7upeXQ80PiNKTu
rtx7DeCVCbZp1L1jcro6A4IaDMgjeAIb/oWC/lG+xOz+s1DECi0=
=uenj
-----END PGP SIGNATURE-----