-----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/jalu9uZGunHyUIFAmpx8loACgkQu9uZGunH
yUKU7w//Rpc+KQr4feehLQJLQLMeFiRRkiQ7SQ8b0W3TromBIwnKscPefdtpgjyT
ZY/785nyEj5rghteyKXRcg5zckfo/GIldhttLvRak48AUhPn/uvHU0qi5eOwBrPh
T1NcELipN2JQEnvrriMcauqcg+KhxVnKms2WbOKeplOMNOfMoGnc6YD8JW6hJooQ
VR0u2FO2vVuHZV29w8nS94sYStLUlTWqcmPDRHSS0cYR7yxdQl15noZuSy88AZsY
rDLTNwfR3OY0YR+5V+oUG0uGMuzLGioSozcEqCCQKipTrBTKqdytPQUXXNp68WU7
GJYWXt/WWPMote33tu02O9E+YhDm5I848Lw1vemNM/Unz0aQhKiHGNXkJV83EBSm
GCZoWUNozl5lIIWBaUf/meK+hdpZwni7qzZjpCg/PSy1ycDmCEG3TKON8nyaUlUM
9H8UYD/lC1LL9kN1BaAiBXMi0DvN8wMUKzi9XTxYr9g93CytyhgqQCuNB5K47SaH
cFYb50SYjkk2UoG6rKI/up50TkDhxu1kR/8G9MeeX39B4avDba/ZJCcHE37bvU9t
N5d7whkh/xum5oHmEtmPWNxXFYaQY2LZDE4CaXDLySTj8BtALOjwc+2aaVGBndAf
IifI92+faQMZsu4iGfQ7+nA/ecydwMXAJesQefmRtAlyFJtywn0=
=mzvf
-----END PGP SIGNATURE-----