Installation guide

6. Press y to confirm your decision.
7. Provide a User-ID containing your name, your email address, and an optional comment. Each of
these is requested individually. When finished, you are presented with a summary of the
information you entered.
8. Accept your choices and enter a passphrase.
Note
Like your account passwords, a good passphrase is essential for optimal security in
GnuPG. Mix your passphrase with uppercase and lowercase letters, use numbers, and/or
include punctuation marks.
9. Once you enter and verify your passphrase, the keys are generated. A message similar to the
following appears:
We need to generate a lot of random bytes. It is a good idea to perform some
other action (type on the keyboard, move the mouse, utilize the disks)
during the prim e generation; this gives the random num ber generator a
better chance to gain enough entropy.
+++++.+++++.++++++++....++++++++++..+++++.+++++.+++++++.+++++++ +++.
++++++++++++++++++++++++++++++++++++++..........................++++
When the activity on the screen ceases, your new keys are placed in the directory .gnupg in
root's home directory. This is the default location of keys generated by the root user.
To list the root keys, use the command:
gpg --list-keys
The output is similar to the following:
gpg: key D97D1329 marked as ultimately trusted
public and secret key created and signed.
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 com plete(s) needed, PGP trust m odel
gpg: depth: 0 valid: 3 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: next trustdb check due at 2013-08-28
pub 2048D/D97D1329 2013-08-27 [expires: 2013-08-28]
Key fingerprint = 29C7 2D2A 5F9B 7FF7 6411 A9E7 DE3E 5D0F D97D 1329
uid Your Name<[e-mail]>
sub 2048g/0BE0820D 2013-08-27 [expires: 2013-08-28]
To retrieve the public key, use the following command:
gpg --export -a 'Your Name' > public_key.txt
The public key is written to the file public_key.txt.
This public key is quite important. It's the key that must be deployed to all client systems that receive
custom software through yum . T echniques for deploying this key across an organization are covered in
the Red Hat Network Client Configuration Guide.
Red Hat Satellite 5.6 Reference Guide
62