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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmqeK3EACgkQu9uZGunH
yUI+8g/9Fzm1C625wC4wKAtIARuzJUMF9HUEBTBDyZXFk9/4nEt81HqNVxnRfck7
TnxA3noecpaCIz3wdJVmPhUJ7KWfsf2EgubeFKcIvKt0uDLA+kBCzEJZ4XLrIFQo
O0v+WEJJBH1iVzzzdwL0dlC3pW+FPZRAtkdlult+sYDrsSyHUqIeZ5r2W7OOFRMO
CxHi+N3ipNDeyZ3KZuqNXGko6X/Xw9gRwsE1LDAZUyj9AIorEO3g9HZtUT1Ld3+K
B7dVIO1OFizBYmLLQY30CadhX7Xn9rgez1oCG/tFukwUPqA2D0jJKCdcHoo+nIN7
4orRSHeEftsFwLh3ElZKb4JadIUNYHwThbiMjooKBJWUsVN0cjVUfX6LpXfKrVkZ
TfuSCX3LevQ6WW9xIJnLWQQRgzMDTZJFA7yADgFD5ALIaH2JLxYC0MDi0t8xuUFU
srb58HhWfdOtBxfcqot5QW3F4VeoKuk3Nr5LT51gFE3DG3CBLMadULEXfiUZKER5
d3rVsUelX/cORRnO5j5enhIebdMRkVdqwHbq5t2FEZ+SZoUEv/RlXDgnEbFAV8QA
CcezWsYlf5fpCSHBT6bT7cCE91g+vRFcRSxiuTirfj2rmEat2PDGHGyeyOzxqdz5
CvRvHCRlDSEuN05VdWvROkF6fUEoQ0j5BObvq1c7pDPYbgG4sWE=
=5Zbp
-----END PGP SIGNATURE-----