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

md5:
e278028e50b73b55cd6a06d0c5bb3524
sha1:
dc11ccf4657fa4ac008ee5ddb89c27e40b7477c9
sha256:
2ba029d1c84724f79740c0296244fd6056f12aa1be1925134d9141f9d036ac0b
sha512:
279bd76c4abda7efcfc181ce35ac993a99a11d60d34283d0e7b0d15443a6ca1e1c6b75444193c075f865bfa0f8b574189e6e91e6980b89ee767ee5874b7f5b4a

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/jalu9uZGunHyUIFAmijgeoACgkQu9uZGunH
yUJImg/+OGVm3/eqm9xboXa4wK4ruaM16dhDtstmy4dRZqR+yJh8fMAmzbsUkJay
64lBhOHaw3DD+JNWCGSRf6iHawYDq6Whir2HukUnfiptznqehw+321supLs0HHt2
RusRCM7fyX36yngbeuUw4IyzboXIvX/BbJHfE291u2G/yH4Jmc6qWArNsyau37Fg
VR9sKnpiFYwTCGSq0JllRNO0r8A71v/CUt+J5zgxh+gOyqOmHg+3YeLAbnpYrbJV
zIMPomnRjhlH1jFE+HEzRt5sQp9Mo8pZDYahqo1L4J0hb6I0AGf4uY+uunv/XWRS
Wjid9FrpufVS7dsOrjGwxh6r3GgNCrWwyyGUWgPGbPeboU1LzGDsuU6OBvZUgzbk
3tjgZv319uD1IKNH5q58qvBL9aUle+W5Qi99vXiZ4FckmFgFa3apEHR1m3AVSx1N
KtzCmYdD/NKHZ97SW6twX9CGzR7A21/v1zzkOgpgIOeKyvxBTlFvDv70dczi6RIy
dTb8wk4Ifv5gxuXLoc/Fr0jwaa8ouLfkka4XbELx+4XyHwPPGnsXWLXdTTSamNPV
N/JSEv9v/IUutTnrvHurJx3v/OjrWpkIYdL0jlDxAjF/3Ho88kIm5ywLZ4HBO3PG
eYiRnWi6k14nPD2VKrkn7AF50r0MqDu/nrhBxlxfId7Pezafhk4=
=512Z
-----END PGP SIGNATURE-----