1RPMSIGN(8)                  System Manager's Manual                 RPMSIGN(8)
2
3
4

NAME

6       rpmsign - RPM Package Signing
7

SYNOPSIS

9   SIGNING PACKAGES:
10       rpm --addsign|--resign [rpmsign-options] PACKAGE_FILE ...
11
12       rpm --delsign PACKAGE_FILE ...
13
14
15   rpmsign-options
16       [--fskpath KEY] [--signfiles]
17
18

DESCRIPTION

20       Both of the --addsign and --resign options generate and insert new sig‐
21       natures for each package PACKAGE_FILE  given,  replacing  any  existing
22       signatures.  There  are two options for historical reasons, there is no
23       difference in behavior currently.
24
25       rpm --delsign PACKAGE_FILE ...
26
27
28       Delete all signatures from each package PACKAGE_FILE given.
29
30
31   SIGN OPTIONS
32       --fskpath KEY
33              Used with --signfiles, use file signing key Key.
34
35       --signfiles
36              Sign package files. The macro %_binary_filedigest_algorithm must
37              be set to a supported algorithm before building the package. The
38              supported algorithms are SHA1, SHA256, SHA384, and SHA512, which
39              are represented as 2, 8, 9, and 10 respectively.  The file sign‐
40              ing key (RSA private key) must be set before signing  the  pack‐
41              age,  it can be configured on the command line with --fskpath or
42              the macro %_file_signing_key.
43
44
45   USING GPG TO SIGN PACKAGES
46       In order to sign packages using GPG, rpm must be configured to run  GPG
47       and  be  able to find a key ring with the appropriate keys. By default,
48       rpm uses the same conventions as GPG to  find  key  rings,  namely  the
49       $GNUPGHOME  environment  variable.   If  your key rings are not located
50       where GPG expects them to be, you will  need  to  configure  the  macro
51       %_gpg_path to be the location of the GPG key rings to use.  If you want
52       to be able to sign packages you create yourself, you also need to  cre‐
53       ate  your own public and secret key pair (see the GPG manual). You will
54       also need to configure the rpm macros
55
56       %_gpg_name
57              The name of the "user" whose key you wish to use  to  sign  your
58              packages.
59
60       For  example,  to be able to use GPG to sign packages as the user "John
61       Doe <jdoe@foo.com>" from the key rings located in  /etc/rpm/.gpg  using
62       the executable /usr/bin/gpg you would include
63
64       %_gpg_path /etc/rpm/.gpg
65       %_gpg_name John Doe <jdoe@foo.com>
66       %__gpg /usr/bin/gpg
67
68       in  a macro configuration file. Use /etc/rpm/macros for per-system con‐
69       figuration and ~/.rpmmacros for per-user configuration. Typically  it's
70       sufficient to set just %_gpg_name.
71

SEE ALSO

73       popt(3),
74       rpm(8),
75       rpmdb(8),
76       rpmkeys(8),
77       rpm2cpio(8),
78       rpmbuild(8),
79       rpmspec(8),
80
81       rpmsign  --help  -  as  rpm  supports  customizing the options via popt
82       aliases it's impossible to guarantee that what's described in the  man‐
83       ual matches what's available.
84
85
86       http://www.rpm.org/ <URL:http://www.rpm.org/>
87

AUTHORS

89       Marc Ewing <marc@redhat.com>
90       Jeff Johnson <jbj@redhat.com>
91       Erik Troan <ewt@redhat.com>
92       Panu Matilainen <pmatilai@redhat.com>
93       Fionnuala Gunter <fin@linux.vnet.ibm.com>
94
95
96
97                                 Red Hat, Inc                       RPMSIGN(8)