Signing Packages - Red Hat NETWORK 3.7 - CHANNEL MANAGEMENTT GUIDE Manual

8
Is this correct (y/n)?
Press [y] to confirm your decision.
Your next task is to provide a User ID containing your name, your email address, and an optional
comment. Each will be requested individually. When you are finished, you will be presented with a
summary of the information you entered.
Once you accept your choices, you will have to enter a passphrase.
Tip
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.
Once you enter and verify your passphrase, your keys will be generated. You will see a message
similar to the following:
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 prime generation; this gives the random number
generator a better chance to gain enough entropy.
+++++.+++++.++++++++....++++++++++..+++++.+++++.+++++++.+++++++
+++.++++++++++++++++++++++++++++++++++++++..........................++++
When the activity on the screen ceases, your new keys will be made and placed in the directory
in root's home directory (since you are running the command as root). To list your keys, (still
.gnupg
as root) use the command:
gpg --list-keys
You will see something similar to the following:
/root/.gnupg/pubring.gpg
-----------------------------------------
1024D/B7085C8A 2002-02-18 Your Name
pub
sub 1024g/E12AF9C4 2002-02-18
To retrieve your public key, use the following command:
gpg --export -a 'Your Name' > public_key.txt
Your public key will be written to the file
This public key is quite important. It's the key that must be deployed to all client systems that will
receive custom software through
are covered in the Red Hat Network Client Configuration Guide.

3.2.2. Signing packages

Before you can sign packages, you need to configure your
ing:
%_signature gpg
%_gpg_name AB6E2B72
you@example.com
public_key.txt
. Techniques for deploying this key across an organization
up2date
Chapter 3. Building Custom Packages
¡
.
file to include the follow-
~/.rpmmacros