1RPMSIGN(8) System Manager's Manual RPMSIGN(8)
2
3
4
6 rpmsign - RPM Package Signing
7
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
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 To create a signature rpm needs to verify the package's checksum. As a
26 result packages with a MD5/SHA1 checksums cannot be signed in FIPS
27 mode.
28
29 rpm --delsign PACKAGE_FILE ...
30
31
32 Delete all signatures from each package PACKAGE_FILE given.
33
34
35 SIGN OPTIONS
36 --fskpath KEY
37 Used with --signfiles, use file signing key Key.
38
39 --signfiles
40 Sign package files. The macro %_binary_filedigest_algorithm must
41 be set to a supported algorithm before building the package. The
42 supported algorithms are SHA1, SHA256, SHA384, and SHA512, which
43 are represented as 2, 8, 9, and 10 respectively. The file sign‐
44 ing key (RSA private key) must be set before signing the pack‐
45 age, it can be configured on the command line with --fskpath or
46 the macro %_file_signing_key.
47
48
49 USING GPG TO SIGN PACKAGES
50 In order to sign packages using GPG, rpm must be configured to run GPG
51 and be able to find a key ring with the appropriate keys. By default,
52 rpm uses the same conventions as GPG to find key rings, namely the
53 $GNUPGHOME environment variable. If your key rings are not located
54 where GPG expects them to be, you will need to configure the macro
55 %_gpg_path to be the location of the GPG key rings to use. If you want
56 to be able to sign packages you create yourself, you also need to cre‐
57 ate your own public and secret key pair (see the GPG manual). You will
58 also need to configure the rpm macros
59
60 %_gpg_name
61 The name of the "user" whose key you wish to use to sign your
62 packages.
63
64 For example, to be able to use GPG to sign packages as the user "John
65 Doe <jdoe@foo.com>" from the key rings located in /etc/rpm/.gpg using
66 the executable /usr/bin/gpg you would include
67
68 %_gpg_path /etc/rpm/.gpg
69 %_gpg_name John Doe <jdoe@foo.com>
70 %__gpg /usr/bin/gpg
71
72 in a macro configuration file. Use /etc/rpm/macros for per-system con‐
73 figuration and ~/.rpmmacros for per-user configuration. Typically it's
74 sufficient to set just %_gpg_name.
75
77 popt(3),
78 rpm(8),
79 rpmdb(8),
80 rpmkeys(8),
81 rpm2cpio(8),
82 rpmbuild(8),
83 rpmspec(8),
84
85 rpmsign --help - as rpm supports customizing the options via popt
86 aliases it's impossible to guarantee that what's described in the man‐
87 ual matches what's available.
88
89
90 http://www.rpm.org/ <URL:http://www.rpm.org/>
91
93 Marc Ewing <marc@redhat.com>
94 Jeff Johnson <jbj@redhat.com>
95 Erik Troan <ewt@redhat.com>
96 Panu Matilainen <pmatilai@redhat.com>
97 Fionnuala Gunter <fin@linux.vnet.ibm.com>
98
99
100
101 Red Hat, Inc RPMSIGN(8)