-----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/jalu9uZGunHyUIFAmq73CsACgkQu9uZGunH
yUL8wRAAhOoGSGwxx1lYmpvscrkwiErfT4trgdYFYMD7mCq5xKrh0H1MfSgIaqkr
Ym8z/Yot+tiqukq67qtz5Rijsx6phdoTW1Jdqid8Fvc1QovD1IdOMwY7jObKzfqL
aD1Lc/YG+I0zg1TYnb9VEYm4tL4VL8YAbFpQA7YiLVGhwlJlRU5xg0KyyWbXVRRB
OLq9yyP9hIF/3Y+VtaOnLmNYUwB45RcyXqR1hEyblpsxezmwGPNiNl2xAjyZyF0+
CJyHUXnh7OTOwBWrUkFuaMGZiahlDsfuWu+JOq733ngq2+WDcMrFNg0ZAc2d3eIV
nX1SkTdJ0h/+Gs+koUrYq90n2wb9+kUlcNk6coJ5Hw5F1G+dx4Ez26xYr0QPfA+Q
+qxHTkd4OBkr0HJmvc+RRXeLxpXn2ENX8ejt84sLOWhnCZmReRmPmSIT71TiG/YS
wrz3fhmaY0MomED2rH/10d1H4QihH4HagYI0HyQTr3dRGNrIZJXoD64DoUdoydJD
ggr9UI3c3ejPatj89QpuJAUSM7fmBu8Vtqj2Taq1r5Ujn1gb6b1vijd1EzU8FEjy
EOVWQYDprYFMPXR1Oz1W7bfHZYFHYAK6e/nMCqYsj1fQ33VN4Qo3A+aBcYq0P2qH
vuQN/uTG6GmfqQvbwf+akVkzxGGaqQSKvaGunhB34feaSZliC7Q=
=v285
-----END PGP SIGNATURE-----