-----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/jalu9uZGunHyUIFAmpzO+IACgkQu9uZGunH
yUJxBA/9GVldmhbesFEfLj/009EY/aDKAg4aMKg9KRBDne0IJDPo2YwJeHIaVYsd
8aiRE0ya24fopoYhrsd2TrIhonM373MLqC8l/TwlgBe0IyZolwekUOQSHJruuCsV
MTHkkP1l8OdUK+UgrCblTKJQy7m4r43wgtahKRRAKNBL2jgwRZNaxQh8umT73gix
jzyIN8JTaZK4C3u9u+l9PxTxy5oWULZHAPeQrRGr0JtZ5TQbT3tf/zPmNIM18TlF
uwnDXMRgPT4yvsicDuM06742wM1f28b9LjNLKy6IdLnD67CCqy661KRSmcDqDSp2
4BryYEz4yIVDvO89BR+kD7wSbGjRty4ZaVLiRIjQysKpx4nDf49dZ9xc9BgWzFN+
w2Z/0aiuJ8Z4qSn3TfHh7P41hFPfj/8EmxEycq4S7pndYLnOSQZruNkx/fhKD1w8
9UKtUTDWWJ6ir6yES1sBDb1IoWH9/RnZDZKO8pAv3Uee7SaPnf7v+kjgX6tfwIfy
3yzCvG31pmhcLn6WIt6HfVWDQsgJYomkQ8bJNf3R+WmwKXmxmpkGU24l1vM5AtS3
iLP+OoDjbMVjm4vEcljEem3QV2XBWV5chl3u4Owqs6/OWaTbk/SbK2xIcL/Nhb6e
sRgZtbPyBxeX2Bj4PD+3IMSNZM9X2iavckftlAD+AHWXok3GBO4=
=z7SG
-----END PGP SIGNATURE-----