After you have downloaded that specific file, you can create a sha1-sum
using
Code:
> sha1sum gnupg-w32cli-1.4.1.exe
If you get the same hash, you can be sure that the integrity of the
file is given. However, can you trust that sha1-hash given of the
webpage? For example, it mightbe possible that someone launched
a man-in-the-middle attack and changed the file as well as the sha1-hash.
authenticity
To make sure, that the file and hash really come from the gnupg.org people,
they signed the file. The signature file for gnupg-w32cli-1.4.1.exe also
is available on the webpage.
How does that work:
The gnupg.org people encrypted the sha1-hash using their private key.
It is possible to decrypt the ciphertext using the public key of the
gnupg.org people. If the ciphertext can be decrypted, you have authenticated
its origin, because the private key is supposed to be known to the gnupg.org
people only. If you already have installed another gnupg-program, you can verify
the signature using[5]
Code:
> gpg --verify gnupg-w32cli-1.4.1.exe.sig
See the readme.txt file in the gnupg package for detailed instructions how
to import the key of gnupg.org (Werner Koch (gnupg sig) <[email protected]>[6]
and to verify it.
Digital signing thus allows for integrity, authenticity and nonrepudiation!