-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmjLVtsACgkQu9uZGunH
yUK6jRAAsNSQ+QxAl8ikL6E9FrmipvZSy/QGAVxDyZvXe8ctxwTSxnq2NH7iKCAy
B9MY2UwiYqGguQa82GxFFA76E/XpdDuUv7e9riNNbCv+b6iLePXHYdXILaS2WTPt
EdsAtazzpeb5HwG/g0FsRQ5LwgGmvh+T4GCwOY2c+kLLFCy1gvakNnWxBHdBfNpa
Ae3/X4Gx+OlmXRzMagDiBmTsHyWMQyuzdlGlPJwOVPptZvKI+NHyEr5i+zxEg1hr
ej1r+STnNDH9DFQGImcE8S23ru/UXvJOC+6ieos4ehRKRCqRIwqd0DO2UF1Z6UzV
+xBmq0NNllPnAgwiI42rVNeNT6RjyKHALqodzO+WizbpVjZC//knoS63FSHDtfVb
A02jf79PgyOsi/UA2Os/j4/iiRb+O425zxdb5maAumfZ2YSRDDGL5gJrG1uTWTVv
vo03oS/zrnBGpvATcHFiKhawEbBgkJHTt4xD5eldgYFnUxKNls4y5vOGYdY7saaD
tXXe1zEW1Q7n1GItJRP1LiHeCv4Y1zOIb5uY7BgXoeX0zlQKu8EfYaE2ZXX1Dt2U
WbSKQjLzdQvU2YGcl8cy+Vei8WCdDtvuFckc5t+MS1Tbs06LU9m1bmYUZGRd5vQl
OzCrVHi1X3OFZy+8hoUiGwiPyS6LNat6SRal56gW8CiMxNlrKA8=
=KDST
-----END PGP SIGNATURE-----