-----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/jalu9uZGunHyUIFAmqFR8oACgkQu9uZGunH
yUK3hA//T2LjA8ei734030vpD24Qm2m43g8JNXekGr/hyXypvAdhg5BOQas4bMqV
TCJXzuUHytCW/mUSam5RXRBVtQl+QkUMbrXkB0kSm3dPxrSaBxlokNdQZ4EptaJ5
d7+TR4y8fTqOA3kKMcZZYc072oZsCt87+u0+KkYuqiBLlYdkpxFiM24jR4XpBRVG
qHu1a6f/QuA9uoULxozNirkTDrz2rDxQgxS2XxRDkqFo9cxcxFv81AKpKL36IxGt
bRRrfHY0U6ZyKd/X5xvWY0I+WMuBNizlcA5TdYGz5JvdZRqF6/ahQzN1I4Q5C9R7
U42+zuI8arXyNJS9ZjZU5xPbKT0ufaxNJhHS9BuPWvRHtjXml8GXsgk55fZCzgbT
xSjM70i0SOa7QoqqaHx3Ccwc+LpIS+2TcGX0IxqaEoMFta6L75mZPnL+X6QGM0I+
ttINf6Oahw1mMM/FUGrYL5DrjPjSjMvH0FYC+FWvoXcCcrT9vdhtN1ayDVVetrw8
NsU4bDW4/LKWS3iK2WcxKSXCCH/GnyPD7P1Bq1MIEUM/2ODqNIYQCoWB+wWmdnG7
bnpXV4Artr5oYg88ZKSbJRptlKaiwi3ne6DayowUOitjhfAb03iMgVHMexiv12t7
EqlEuipeGVTLfheQuC9dkhhnJy2Cg0lp9wrfXKDje8Nuto09UE4=
=rAGz
-----END PGP SIGNATURE-----