NAME<\/a> rpmkeys \u2212 RPM Keyring<\/p>\n rpmkeys<\/b> {–import|–checksig<\/b>}<\/p>\n The general forms of rpm digital signature commands are<\/p>\n rpmkeys –import<\/b> PUBKEY …<\/i><\/p>\n rpmkeys<\/b> {-K|–checksig<\/b>} PACKAGE_FILE …<\/i><\/p>\n The –checksig<\/b> option checks all the digests and signatures contained in PACKAGE_FILE<\/i> to ensure the integrity and origin of the package. Note that signatures are now verified whenever a package is read, and –checksig<\/b> is useful to verify all of the digests and signatures associated with a package.<\/p>\n Digital signatures cannot be verified without a public key. An ASCII armored public key can be added to the rpm<\/b> database using –import<\/b>. An imported public key is carried in a header, and key ring management is performed exactly like package management. For example, all currently imported public keys can be displayed by:<\/p>\n rpm -qa gpg-pubkey*<\/b><\/p>\n Details about a specific public key, when imported, can be displayed by querying. Here\u2019s information about the Red Hat GPG\/DSA key:<\/p>\n rpm -qi gpg-pubkey-db42a60e<\/b><\/p>\n Finally, public keys can be erased after importing just like packages. Here\u2019s how to remove the Red Hat GPG\/DSA key<\/p>\n rpm -e gpg-pubkey-db42a60e<\/b><\/p>\n popt<\/b>(3), rpmkeys –help<\/b> – as rpm supports customizing the options via popt aliases it\u2019s impossible to guarantee that what\u2019s described in the manual matches what\u2019s available.<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
rpm<\/b>(8),
rpmdb<\/b>(8),
rpmsign<\/b>(8),
rpm2cpio<\/b>(8),
rpmbuild<\/b>(8),
rpmspec<\/b>(8),<\/p>\n