-----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/jalu9uZGunHyUIFAmrtNPAACgkQu9uZGunH
yUIV/xAAhswe8U+FtNAXjEcFQgIarrA4+1x9bihgldZCERxiFCz6h7brsIIlKkr4
SrzHBpKkngjQRruUuW830bHpuuCSwrEfojVKW9CKeC7khG7PV49JAgQjNHg4H+5L
/WRXm3937+kJRU/i7xuUNpq9KEqIMVDm0jWnxKYiIMdQWpkmKNP7wF5ThZvgIWRh
xRrsmhCU1XocRcbn1IOHGWTPQNDUtNoTWhRcf9cOpVld5CGAYr4Ne4HEm+M3Rauq
Iqb19eOBeJAeYnbmA5ravfOJYVYxUS4/HTj5mZ0tqMbnND5SGlgbJJ66btO+rIEV
yLgoCamSpCXFv6aR897XhzO0IYGlQeem88FoeBUTS76NWEpiX31abhKQfrqAiz5k
FQMi13WZEV9qcvI06iIPcP+83VEE1nyXVTNQdbAvG/wDjg+PK5TS8kCPo+Bq2XIQ
kTiLV22WdWMtBCMYgbrDuO5zyHyC0x4+LDsqEk/mn7b+FmkEYmOtUGOffdE8/sif
ynANY5LsahuYxAQWBgSbL0EcMECyui/KNtDt7qU2iS06HH63FYvXBeCpX6CvacG3
szO0ScCvuPqHTr/kxd/0kLMYJTTJWbpUe/egll40Ng881+fXHWrDVociIJHIKrZs
CExSJx9DLtqlWZuYejKZp1y5g1zOU5FmMjpwpQ+SxgC8mDz03Dc=
=2kIL
-----END PGP SIGNATURE-----