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

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrxgRgACgkQu9uZGunH
yUI+xg/+PI3fCmncYzGh0mfzHo/y822SkJIP2GFlyrjmvk3lzl4u4cwNpkz/gY56
ozewQkxoekr8NSi1WLsomps3hTXDzFi5CQ9yKmG+k9Z/vCSLFpH7x4ulXL1Pqw1r
Vt26YlrtzQJMwRURpogSUuLk3c31qJGog37/0HwpKliOazNYBzeJfQ9rTOhtTKf9
4Z/Kfc6Hz/V2xw00xmEtoIIQDqbZKMPFPN7B5vPXwcj5/2EqqCBh8JXEDMRbq/Pu
q+Q5TqckCBp5N3ZctpNAZT60QZfunAZNueEOoH9iTMUyGC+c4EQX+eVfsnPGRVjS
fQdmtIOl8Zi5avIY9qa2muVe5X8hwvP1sVYQYD/8pySurj8spU5aH6bH2CMNQbmF
4/hGv35I+JrBd4JYvvUoxQG6AUhxCrmb+vOM496bTraR2qIIEcQUOELfB9heCnSI
DwmdaxgDSN7qmI2lBdan26uvO5V9rPp99vvSL8YpXqgLtzbDyyf1z+lqn7GRrHfP
6Jo33/4qCePTNEP0OTGXHuYjR8O3DEV4rifo8GcbgiB+pfBEYyJ1wX+4Ht0nVV/A
BQeC+A66gci8CjoNZ0l1MOeeflRxaDL5wI2bYfVcF8fU+t05kDAi7BsD84q8Fuz3
TTJ1alcinr9Asq8PsmKxbKkdJxNl+wMCsQr6WoRUdmQKhzK7MtU=
=SM0z
-----END PGP SIGNATURE-----