1RPMKEYS(8) RPMKEYS(8)
2
3
4
6 rpmkeys - RPM Keyring
7
9 rpmkeys {--import|--checksig}
10
12 The general forms of rpm digital signature commands are
13
14 rpmkeys --import PUBKEY ...
15
16 rpmkeys {-K|--checksig} PACKAGE_FILE ...
17
18 The --checksig option checks all the digests and signatures contained
19 in PACKAGE_FILE to ensure the integrity and origin of the package.
20 Note that signatures are now verified whenever a package is read, and
21 --checksig is useful to verify all of the digests and signatures asso‐
22 ciated with a package.
23
24 Digital signatures cannot be verified without a public key. An ASCII
25 armored public key can be added to the rpm database using --import. An
26 imported public key is carried in a header, and key ring management is
27 performed exactly like package management. For example, all currently
28 imported public keys can be displayed by:
29
30 rpm -qa gpg-pubkey*
31
32 Details about a specific public key, when imported, can be displayed by
33 querying. Here's information about the Red Hat GPG/DSA key:
34
35 rpm -qi gpg-pubkey-db42a60e
36
37 Finally, public keys can be erased after importing just like packages.
38 Here's how to remove the Red Hat GPG/DSA key
39
40 rpm -e gpg-pubkey-db42a60e
41
43 popt(3),
44 rpm(8),
45 rpmdb(8),
46 rpmsign(8),
47 rpm2cpio(8),
48 rpmbuild(8),
49 rpmspec(8),
50
51 rpmkeys --help - as rpm supports customizing the options via popt
52 aliases it's impossible to guarantee that what's described in the manu‐
53 al matches what's available.
54
55 http://www.rpm.org/ <URL:http://www.rpm.org/>
56
58 Marc Ewing <marc@redhat.com>
59 Jeff Johnson <jbj@redhat.com>
60 Erik Troan <ewt@redhat.com>
61 Panu Matilainen <pmatilai@redhat.com>
62
63
64
65 29 October 2010 RPMKEYS(8)