-----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/jalu9uZGunHyUIFAmr0Ma0ACgkQu9uZGunH
yUIbSQ//Xxdir/SLxfJ7gCW6TPAFTUYajOJl0yQM/t66UPtfhZl1xL06WnqNlCQk
utLhTRdkHRpl2kAhm8oJBVL2pZLyslGBLvHHBt3t10+C9drFQtzIKs+wNuSkR1/O
sivGoSXZy++/s35RLhlpjorObNzgnzu6iOTQfvBTiER9kOiI9Zase7xwnQMzKxwk
pGDm0NIlDmVq8cr3xvKe6md7nJVVJDWCl1dH3pBgsnDzfqAszFZzPqa2EvtVPsI5
fUxkLwJ8kI448miPO27WXK7jZO7ZmaoVOCVU9LZ+3qacyjNvrCHMmbNOU/w4D+WC
2sBVBSRGQgG7dCEsvKuTCUxlDFxzYgS+8y0DT+BMGWhFk+ykZC/LBC7oQrMa3IVE
lM3/cMpThecc1h9e5c6kMk5XbAIYU2ZoHthX/F8O3O322N/Ic3onrRRo/dNLk7xi
9tfL/2uJpmxP9vWfuUnzC4E9m97dL/IN5wvXREhzhffnS1Y+ynQEzQygv5qdwDcA
DdTCAgzA7GQ+vQPDwCNRCGdDlnolUJLKjZLz4TN7/WaaN8lPG7hkvIApyfNdfsPK
iOkGIeWQBJAJoezoWJpKuStBXiMowu4RuYDdXhwGf3z4gbe+GGwVXnq4CjKMuRc6
dgJ8o3RyEHgc0Zy+4iGv7b2nGZqWR+Ht5mXsVvuvnaFBKCArwoA=
=v8EO
-----END PGP SIGNATURE-----