-----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/jalu9uZGunHyUIFAmr4pq8ACgkQu9uZGunH
yUL0SA//QELMNEnnnfruIC7xlqVKXe+wZ/392whoRl73F6NxOONox9Kq2DWk5xRj
lPbe0MBsTDPYQw1CWRwNWqOicKnmrefup1gFeKvwXKY985H8MrSvHvBQjY1qN0D+
W2ZwvppS9UaT7+Wuu1InN5/jnR1sXQMu2qsPlAj3SQSrNgyNYYGU4L+5amSyUIR1
QaTjPf85yQHo+8uRripZPcZFxrrRYXEYSH6mGjsngVZBOOmUzpKHGtrgOdP6zoRr
8K80eLCymUl92G3dcrNVP5tZ0+LW+EHdz8W0oNUwJV1jY4bF4MPsTzIAkuyOsWyk
5cyU9GR8I20SGNNvBjIJxZHQ366dnyKZuWtt8TXnAalsq3MMHBqQl4tjOo9d6pgy
C9j6T+VF5AIJOr6CKvd3EYjroE4cvipvkary4+M5dENJSCLoblTYMgPsDsqapUcM
YDQKppduNKyFMvV0iG5xxXKVP0Y1Bbwcsu/yPkoYca0pkM0klrJeZ5bJCaXi7erK
fXAII6zP+O4Spk8A9432Z0dKmfgHEw7ZxEA6p1FePa0RY4DRyufZITAhPm3KGX7C
JxUSEi6oJr5xKnWOo6FIWfavqgpYE9pepdeVWvtvRAfgB2yjMMmC6MS8i/0O2d2p
SCQvL5eAwE8MdYAWD++dkscYuD0CUT6jIvhW5301T28P3srm5Ig=
=E69y
-----END PGP SIGNATURE-----