summaryrefslogtreecommitdiff
path: root/doc/rpmsign.8
diff options
context:
space:
mode:
authorPanu Matilainen <pmatilai@redhat.com>2010-10-29 15:14:01 +0300
committerPanu Matilainen <pmatilai@redhat.com>2010-10-29 15:14:01 +0300
commit325a9b1ba5a8a964b4773538cf73d4504aba7c05 (patch)
tree5046195cfa273e8e6538f947358f77ff0230944c /doc/rpmsign.8
parent52724dd5ae4f1633aa49c7007f234887bfdee933 (diff)
downloadlibrpm-tizen-325a9b1ba5a8a964b4773538cf73d4504aba7c05.tar.gz
librpm-tizen-325a9b1ba5a8a964b4773538cf73d4504aba7c05.tar.bz2
librpm-tizen-325a9b1ba5a8a964b4773538cf73d4504aba7c05.zip
Add rough-cut man-pages for our new executables
- Chainsaw relevant information out of rpm.8 and tweak a little bit, adding cross-references etc. These will need a lot more love though...
Diffstat (limited to 'doc/rpmsign.8')
-rw-r--r--doc/rpmsign.884
1 files changed, 84 insertions, 0 deletions
diff --git a/doc/rpmsign.8 b/doc/rpmsign.8
new file mode 100644
index 000000000..26797f359
--- /dev/null
+++ b/doc/rpmsign.8
@@ -0,0 +1,84 @@
+.TH "RPMSIGN" "8" "Red Hat, Inc"
+.SH NAME
+rpmsign \- RPM Package Signing
+.SH SYNOPSIS
+
+\fBrpm\fR \fB--addsign|--resign\fR \fB\fIPACKAGE_FILE\fB\fR\fI ...\fR
+
+\fBrpm\fR \fB--delsign\fR \fB\fIPACKAGE_FILE\fB\fR\fI ...\fR
+
+.SH DESCRIPTION
+.PP
+Both of the \fB--addsign\fR and \fB--resign\fR
+options generate and insert new signatures for each package
+\fIPACKAGE_FILE\fR given, replacing any
+existing signatures. There are two options for historical reasons,
+there is no difference in behavior currently.
+
+\fBrpm\fR \fB--delsign\fR \fB\fIPACKAGE_FILE\fB\fR\fI ...\fR
+
+.PP
+Delete all signatures from each package \fIPACKAGE_FILE\fR given.
+
+.SS "USING GPG TO SIGN PACKAGES"
+.PP
+In order to sign packages using GPG, \fBrpm\fR
+must be configured to run GPG and be able to find a key
+ring with the appropriate keys. By default,
+\fBrpm\fR uses the same conventions as GPG
+to find key rings, namely the \fB$GNUPGHOME\fR environment
+variable. If your key rings are not located where GPG expects
+them to be, you will need to configure the macro
+\fB%_gpg_path\fR
+to be the location of the GPG key rings to use.
+If you want to be able to sign packages you create yourself, you
+also need to create your own public and secret key pair (see the
+GPG manual). You will also need to configure the \fBrpm\fR macros
+.TP
+\fB%_gpg_name\fR
+The name of the "user" whose key you wish to use to sign your packages.
+.PP
+For example, to be able to use GPG to sign packages as the user
+\fI"John Doe <jdoe@foo.com>"\fR
+from the key rings located in \fI/etc/rpm/.gpg\fR
+using the executable \fI/usr/bin/gpg\fR you would include
+.PP
+.nf
+%_gpg_path /etc/rpm/.gpg
+%_gpg_name John Doe <jdoe@foo.com>
+%__gpg /usr/bin/gpg
+.fi
+.PP
+in a macro configuration file. Use \fI/etc/rpm/macros\fR
+for per-system configuration and \fI~/.rpmmacros\fR
+for per-user configuration. Typically it's sufficient to set just %_gpg_name.
+
+.SH "SEE ALSO"
+.nf
+\fBpopt\fR(3),
+\fBrpm\fR(8),
+\fBrpmdb\fR(8),
+\fBrpminstall\fR(8),
+\fBrpmkeys\fR(8),
+\fBrpmquery\fR(8),
+\fBrpmverify\fR(8),
+\fBrpm2cpio\fR(8),
+\fBrpmbuild\fR(8),
+\fBrpmspec\fR(8),
+.fi
+
+\fBrpmsign --help\fR - as rpm supports customizing the options via popt aliases
+it's impossible to guarantee that what's described in the manual matches
+what's available.
+
+
+\fBhttp://www.rpm.org/ <URL:http://www.rpm.org/>
+\fR
+.SH "AUTHORS"
+
+.nf
+Marc Ewing <marc@redhat.com>
+Jeff Johnson <jbj@redhat.com>
+Erik Troan <ewt@redhat.com>
+Panu Matilainen <pmatilai@redhat.com>
+.fi