-----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/jalu9uZGunHyUIFAmp+c5wACgkQu9uZGunH
yULsXBAAi9KWZRjd84VklKdUntaMVAo5Bzf+l12RuAgCK2D25dn8ogBEiRD6RZpc
Z5XMdxDwwbH6q7RtRESwdIRn6WbsnWeretF7nJlslbwau7dAtl7h812xBd+GKRxS
cfusjiYpLsKaVAMZP6rrQ+7jfNET2A1dHmh9gJg6lnFWCJ4HxFBirwxdeGs4I1xw
VfveDd2AHfHCWu4pb+YJJWsIhG6fB/ZY5SiHdaquvwsDBKn6gRctNB5av8i1EU8m
TIG4Jlju1yLXzHeorsZEVsbfhsGhq4SQnqHKPQsIMOUrtEUR2XfY8IQAOjOrvx7F
oZV/FvXYyQW2KFhIRcORTPY6OHdBJuRMWEKkaWhJKBuS+Q91AR7eba5pqHijovG2
a9QA3ewvjGCT4G8pqFD8m1O0E7KOSNm8eCuUV+Exnzm1hoRAJqXg2g+a8yOw4gHU
k4ayF1Bd+Rdw2NaHstWdyiI7VhKIWSW9PetlhuLxeDWViPNjIzS5f6jBcr+U7m0v
PSmZena/FlNFk+s8ZSIWe5yBXD6uO89zfVDKmYwvhp/njZby+55OrKVlmDswMz64
JglpYfPMREl1iHZds63+d65QZRtstSoXlXHaHR6Q88htMQ6YvA1A353u7nqSX/0T
I9s6Q9xk/osM1UJLt5mIru1yTdgNQFJIzM5yDTolLHtHj1RCRyc=
=f/v8
-----END PGP SIGNATURE-----