-----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/jalu9uZGunHyUIFAmqiOCsACgkQu9uZGunH
yUL9sQ/+JFuuTl1GNRjUA5qFRL3aaBRYY8IB+AL/git5wBeyqgyXBRcUf/0gfZGm
7sp4Of7ytFLTJOlQLmO7nja8TdqV7K8loliR9MT3Y3R/xWJU9IhZZdqD4ZdfU7Sa
p84kv0WUX1oy7aBOajGfg3gQyXtSfYRW0DxTHnY6hP/rscOHMBAa4hVlNcNpWOjO
i1ZhjYEHVrhYfOeSovQ0cxYl2piVb6+Z8qwnMC/SUvxrg5pq+kbOps0GUWdHB9rq
q99C7XSofvLt/dxUR2LdqzHUYoJN5uBnn9zwi6sWfZ2UGTS7wYa1XUcZeup1kCs+
X9lZvhkrjJr2D+Y/GTyQ4//4mnjbRXvvocnEzLwWX+uwa35WADt4a/dGoeVwIfLq
NB5ZDr0fndSVa6UTzqEN5JO2eRKk6PpRcT2MWi+kjWRGqE72OhaxA+pMl++z0Z7A
cqFgFU1o8CCgNg8+NsfpAUz24jyRWPl4CG3EPdROyFKxM+935BKKSQlUq0etIToT
jheG3tXEYcYqHEXef/xUjvv87LNNwe6OvSXw+9auIaWcT32ReYJCZis61SBP8WFL
RDwJBKTenudOligSqlJaPyaJJtpBXMxLmFNEc8oE+I68IKsZTy8GiTpR/tBiNEmh
VVSK7HpyDstyL1PDIVbsh/K4Sq8n9ZEuR2Sq6iqepCKWLHQHVeY=
=rf11
-----END PGP SIGNATURE-----