-----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/jalu9uZGunHyUIFAmoJRtwACgkQu9uZGunH
yUKp/w/9Eqo1G6DIAWDvWH33Rl+sWemo4aMUwFfv0TGsPD08CpBys5oLhyWwTFMQ
gYErlE+ZgMgtTznDU0sWTpUsTostC0xtAUu4ByubcqqE6eYNC8kICvCcodPB8NFC
PkpYCPztjKeFoDLG4wuVzUwtmjnvkoS5VUqEeMZboZ51fauH5fWSkXhuZ/akHHwW
UcmrN1DxJcw6SPKsY4PPTfD7bVeeScZ8yjUpKFg8Z0U7+WRDH3hqLe0DhQGSsFQu
goTEq/ihbk2iVYqKrm9mPU4NhtsvC2IWAtn7vs4xx1LTcwEk/yHRbDU88N+s7sfr
cjfHAfRHt0wkJTKo5x9Mu+opjkzMCcC6lXfAka/0vs221dt/VXo6JpwcqsnIn4Jl
w80GaIofE1KMVfJD7PllDOOA8Sy4p8+NLor3GcdbhhQUnD5BBlklH4CB6BaBbuxj
TzP+n93NvGyD1TgaYlj2J6mG27LEdUuURXosRjMq0KnqgL/MReL4yRUaJ1PJK1Jk
O4+SrDee+co1idlvx2K+Ml7eRkAdV9kcdyx+g2xBDWUD0CNH3Z+YxAI7UTHiRx+l
F3HmTq/XKGL0vwIniXJ0PTO/iEN+2Ell5JiqbNgvbwNuiAFUp6RockqxDw1303Al
w6YIzEQdciOhzFd+Q5Du950pNtzT05KHhgJ+pIRhF6ulgIuDqBI=
=oRPG
-----END PGP SIGNATURE-----