-----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/jalu9uZGunHyUIFAmrC4WEACgkQu9uZGunH
yUIk8g/7BFhL/TJUPzpRtNxjOqH33qCS2GDP5YTE93ZbrQhl3HVs+ed+hcFCxp9L
DTadIR5ls7CZRdwKDfwIrLJDxASlH3dunVF240iaI2TfDEB8dcfRqJ3ZX2wnT9K8
dSCh9GxrAwGA9faoc+1okeN/yxQ935DYlNxElu36ce+uqFLajQICST0q6wSJmiA6
w5byWij2nh5sEqglJ2Yh4TxqWt9IKdy4waFKzFVejELHeiKnASI6uguYJ0E5NwjQ
3y0PXfn9fkkPtvfzym+ktqIw8TjRzP34U2xyd94e7Scc9IQyTwsX48R84jqht1mP
O3KGNw40xybDn+oNVN+e1bici4b9lKZwe7+765O96mA8U7XcTyBtVKvjGyCOtL1b
nQfu4p9AUQ+TQ6MQyowz49cYUlk/e3mOEglLpK1JPvTFET8bCt3lsMA/CuYe6/9l
qUf1KGAAKpoP7vbiY+rq0uJ/f8BNjYCdVwdeNNqWk8+UTzU5l2YNF6IC+JbYEkvQ
sNGJ9EiSAPF1NjrwRGVZkOkd2tUeGkg5wbEIJ6T3pSQowlekCZo4dloKfjCIE/JJ
wWtKyvKjRbjbNobSvF5NrqWJaGoX5Kz6VVlTyT5cnKG4upE64rYJN2w1fDjA0NO4
bkvLU9YpZPkMdnL1sbfcyo+1wwfuUsP0JG+ygp4kl2ebsmPkgL8=
=Iu3t
-----END PGP SIGNATURE-----