File Explorer

1/*! \page signatures Signature header2 3The 2.1 release of RPM had a few improvements in the area of4digital package signatures.  The usage of PGP has been cleaned5up and extended, the signature section in the RPM file format6has been made easily extensible with new signature types, and7packages can have multiple signatures.8 9\section signatures_pgp PGP10 11Legacy usage of PGP in rpm-2.0 was cumbersome, and only supported121024 bit keys.  Both of these problems have been corrected in rpm-2.1.13 14Whereas previously you needed many rpmrc entries to clue in15RPM about keyring locations and such, RPM now behaves as PGP16users would expect.  The PGPPATH environment variable can be17used to specify keyring locations.  You can also use a18"%_pgpbin" line in your macros file to specify a different value19for RPM to use for PGPPATH.  If neither of these are used PGP20uses its default ($HOME/.pgp).21 22If you just want to verify packages, you need to supply values23for the macros24\verbatim25	%_pgpbin	the path to the pgp executable26	%_signature	the type of signature to use27\endverbatim28 29In order to be able to sign packages, you may also have to30supply values for31\verbatim32	%_pgp_name	the pgp signature to use for signing33	%_pgp_path	the path to the key ring34\endverbatim35 36\section signatures_signing Signing Packages37 38Signature creation is the same as previous releases: just add39a --sign to your build command line.  You can sign a package40after the package is built with:41 42\verbatim43	rpm --resign <package>44\endverbatim45 46Using --resign removes any previous signature in the package.47To *add* a signature to a package, leaving all existing48signatures use:49 50\verbatim51	rpm --addsign <package>52\endverbatim53 54RPM always creates MD5 and SIZE signatures when it build55packages, which means that packages built without --sign can56be "verified" to some extent.  The MD5 signature should catch57problems like corrupt packages, faulty downloads, etc.58 59\section signatures_verifying Verifying Package Signatures60 61Package signature verification is the same as previous releases:62 63\verbatim64	rpm -K <package>65\endverbatim66 67RPM will verify every signature in the package, which may include68more than one PGP signature.  The output indicates what types of69signatures are being checked.  If any checks fail you'll see a70"NOT OK" message, and you should be worried.71 72If you have a package with PGP signatures, but don't have PGP73installed, but still want to verify it as much as possible, you74can do:75 76\verbatim77	rpm -K --nopgp <package>78\endverbatim79 80That will cause RPM to skip any PGP signatures, but still check81any others (currently only MD5 and SIZE).82 83*/84