-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmqTMlIACgkQu9uZGunH
yUKktxAArLb1/MBjYg88PDgKD0HMezaqEejjidG2Kc+z87Otqnt5jQ7BmzY0hP27
Z7NIszOCN+Y9tdz5WCz49t/NPSMMdNWqkfw8INZFKp2PhVif4tDujhZSJfnuSENK
mYAcPNH7/rkk7rjTrXPHnAgxHmEqDYaSP61qo+RTobRbBbiF+wrJs8UiaNUDPFDd
EkxTeYbJNKmmcrvQhLh/V8a2wH5NOkW0QHJyHGtuayHq/ErhZZp0CdJlMawkJzRV
8t32OwxYvGwrZWNY9ha6W5W65sKQoVLd6nWSbVZX2yy/dbR12OSQhGSXx6im/KRS
MaSe+yoWjISh62Rs8FrlL32iKSOXK3OIegYcLKCltbJRL8azJKATjxk+7v+nuuaY
xxdZe5p9j06StaxGgDtTuQSBBi04CrtRQFyoAMxOzyOk7R+axUsDmBbxrfxd86KO
+XQW/DES5gGcKC98zsMiLdo8AzJw1fawSkXd0D40GwA17xZoenjw1ESJhf7J0arP
Rs3/P0+xvXLnLVKQ69F9Qo7hVRRReBIVPnMDpxhyX6EiDFFTP05GWM936nAP3MQC
OdCVzEqfn10wBZCZphoL14K8LpIQULYW5YXayVQQHh30rlrAXBY35YJF5TOJe8wj
5K3ngIq744cefcb6yjE1jd3EMUuGTSTA0K73yCqlyhYpSxR0A20=
=PUxV
-----END PGP SIGNATURE-----