-----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/jalu9uZGunHyUIFAmqo6NUACgkQu9uZGunH
yUJuZw//afmrcfhZyPTPXI/tmBIEvGSkWx15YopR+DuFKIIdnsdrU1sJNbfXJoir
hXf6sH/nrZeOPQMxSKOWAQr8v2ypzROEtRNNtMFDMq/0/q7scZwYJ3s5viMpjxcR
g5W1/KlW5qJqtyy4tkKKDNlA9hTNTxKXxOfvU6HrTVFE+AazibND2HwE562tpYE3
BDWAYpQUtWbZUbBB0BpfbxXmtdZPdGN2Is88cE5//hRUhFMJ+XhCR0xe1JfQUoY7
D15laEonUHSlPdx37RzsTE5DlunblC3HMwvb6OIWSVjUUHXATPwbppbz3Y+UFjtI
Zf2P9n3yvnzrf+GsjfD6hp0rT23Hdti87XEU/SEP+NPSUl6w6p7SkOLP96d+FqNX
HXbZCcyH5UOLGbPI9iKDe5zLvgrrpokvUd4IOakqIvD1hNxLx4oyd+q9gEmJKP9Y
Bw2QDel70tfWQJJSPuvoEtvBbWNskbjgyqTuWEiiQ6GYsmsRsYYcsheickwJR592
3BGV9Sm+IMWNTSITu+g5m6nb7UK8k0HaZ5c9r9RfGUPkUUXvTb9FxTuk62ZzSEwh
Rd2+aIhCTdPEVXFrq0ykWUCOU7OvIC4lXtjZXtRvZyodyG8TvAQLB+SRTavzr/YC
aRtLEEaM2VO9x7Pe5vjw42OCQ+rIgZlVWT1KriXEfF9hofYlBSg=
=Dm/x
-----END PGP SIGNATURE-----