-----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/jalu9uZGunHyUIFAmnyv34ACgkQu9uZGunH
yUIMjxAAqo0fNLb1AtWmrgfazSqkSnkVtCIMfnEhC52s31cLAuxrIXyJS0oRaKwS
UHhkKWMm0D4mPXhEdTeAlLT0//xHz9KBp/wswTfN3kzu+ZSHmQKkyMxPqAVAsfrF
jJU5Mghdh7PMt+hPFmZQ39K73X/+0uD723rVa7VUBf/Rmubd73lv1Jt/CSO6tPRe
gBNd9LBjPsjjDsxxnH+kq73AH4vW5WtP+6pDdc6E2zAuQ4yXFKb7FGpWSyvNXbil
3LwYd5tlDkU4B+W8MSIzIZM1YXCDyRyqRLHr+IEFC20zD9KDr1StFG7SFN/SFl5B
GqIf3659i6TD95kJ26cFACpueghcQb+vyzSqpvHVekiTIPCVPQdLRNlUMnVvBzVZ
lGGTsL3lYA8J37DTK9aRALvX2eFdOgTBPqvhicri5Iw4Ljex9gtGxyogTdDcSfMr
zXRd4Vaa29W04E0FAUSjnAi6cteSvr3OXQKx3c/QJ7pI79gjjNNXWiaTvwPt3KCw
OjRExawiaIHkmk/rLrVMayCbYpx4iml0nI/0vPfTZ1qKczCX63NHvx58FGb9nOrU
DXQ+PWYUc/lVPX3pAJnKKWOdB+UsDsKdTxaDVofcuRzOB0CufYIyTXZOssK6d84X
gJOojaZrBZ7bwHn+fOfY4JPSZ2GlZ6c2jyXCFMTWWurlZmBWoH4=
=gU2z
-----END PGP SIGNATURE-----