Securities Software (Management & Limitation).Linux GnuPG
The above command will append all new keys to our keyring database and will update all already existing keys. It is important to note that GnuPG does not import keys that are not self-signed. In the above example we import the Public Key file “redhat2.asc” from the company Red Hat Linux, downloadable from the Red Hat Internet site, into our keyring.
Key signing
When you import keys into your public keyring database and are sure that trusted third party is really the person they claim, you can start signing his/her keys. Signing a key certifies that you know the owner of the keys.
• To sign a key for the company RedHat that we have added on our keyring above, use the
following command:
[root@deep /]# gpg -sign-key
As an example:
[root@deep /]# gpg -sign-key RedHat
pub 1024D/DB42A60E created: 1999-09-23 expires: never trust:-/q sub 2048g/961630A2 created: 1999-09-23 expires: never (1) Red Hat, Inc
pub 1024D/DB42A60E created: 1999-09-23 expires: never trust:-/q
Fingerprint: CA20 8686 2BD6 9DFC 65F6 ECC4 2191 80CD DB42 A60E
Red Hat, Inc
Are you really sure that you want to sign this key
with your key: “Gerhard Mourani
Really sign? y
You need a passphrase to unlock the secret key for user: “Gerhard Mourani
Enter passphrase:
NOTE: You should only sign a key as being authentic when you are ABSOLUTELY SURE that the key is really authentic! You should never sign a key based on any assumption.
Encrypt and decrypt
After installing, importing, signing and configuring everything in the way that we want, we can start on encrypting and decrypting our work.
• To encrypt and sign data for the user RedHat that we have added on our keyring above,
use the following command:
[root@deep /]# gpg -sear RedHat
As an example: