-----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/jalu9uZGunHyUIFAmriScIACgkQu9uZGunH
yUJ6Mg//e00KtBGmG9+Xxz+ZaMK3g5lhUGdyzVc/NKh4+K5XBIt8lkTDIKB+R/E9
xnGznZSuLkdG3sSPZrMoDHQ9GfDhFvN9SCIRnDizNkAxTqSdU2jg99uaCTSuVFkA
hAEOypdvCDOEE6VSVjl1wFPvqhFwl4mfmek48UCzUDGMeIY/V/5ZlQcxLXysPk0k
YK7sb4lVaDPN0COXLYUmBVgdv9nqXOAyDErSJ3lOU9hDM2CvGvK5JfH/W5jptt3K
59uf/rKF6SM6YpWtN/r3hHovYC9STB1EHPhy82Bmv3Zr3GWltKY1F0fQ5jX7kJm0
QCW51R8itAaJlZ37rUNOqwp++TLCklV8G/YdMaem8mEhHrXbGaqjbOPkspDwGjfl
C4iheawV/9lVp/w6ccshs1iCqqaZLnmyvtJ9MwnGTk40hvLRZ+g2IShG9yJgmHWy
Vse7DH6Hh12wGGchwQgOeRSZPkfujpPSkt+G1RPaOWcGv0Yq2F4ev8O1oED9xDBf
yD2JpOqE7R5J69ONAHxoTv/hxvwxnkIrhcd2cWJIzjvUXWvJ1zOahjm42Ivvt9/4
E38sQ7y8aY9zNVmGoo7j9hXsE692uxt0HiYmzML2FE+mY6wG9+zY6Fn/eyzS/Q/a
hwRQZ+EhF60pWbdHP35AmCD6GAF+e/MnVouNB5z4xXkVr6n0e98=
=X/eT
-----END PGP SIGNATURE-----