diff options
Diffstat (limited to 'man5/gitformat-signature.5')
| -rw-r--r-- | man5/gitformat-signature.5 | 34 |
1 files changed, 29 insertions, 5 deletions
diff --git a/man5/gitformat-signature.5 b/man5/gitformat-signature.5 index b7dd1b552..208f10ac9 100644 --- a/man5/gitformat-signature.5 +++ b/man5/gitformat-signature.5 @@ -2,12 +2,12 @@ .\" Title: gitformat-signature .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 03/01/2023 +.\" Date: 03/06/2023 .\" Manual: Git Manual -.\" Source: Git 2.40.0.rc1.2.gd15644fe02 +.\" Source: Git 2.40.0.rc2 .\" Language: English .\" -.TH "GITFORMAT\-SIGNATURE" "5" "03/01/2023" "Git 2\&.40\&.0\&.rc1\&.2\&.gd1" "Git Manual" +.TH "GITFORMAT\-SIGNATURE" "5" "03/06/2023" "Git 2\&.40\&.0\&.rc2" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -38,9 +38,33 @@ gitformat-signature \- Git cryptographic signature formats .sp .SH "DESCRIPTION" .sp -Git uses cryptographic signatures in various places, currently objects (tags, commits, mergetags) and transactions (pushes)\&. In every case, the command which is about to create an object or transaction determines a payload from that, calls gpg to obtain a detached signature for the payload (\fBgpg \-bsa\fR) and embeds the signature into the object or transaction\&. +Git uses cryptographic signatures in various places, currently objects (tags, commits, mergetags) and transactions (pushes)\&. In every case, the command which is about to create an object or transaction determines a payload from that, calls an external program to obtain a detached signature for the payload (\fBgpg \-bsa\fR in the case of PGP signatures), and embeds the signature into the object or transaction\&. .sp -Signatures always begin with \fB\-\-\-\-\-BEGIN PGP SIGNATURE\-\-\-\-\-\fR and end with \fB\-\-\-\-\-END PGP SIGNATURE\-\-\-\-\-\fR, unless gpg is told to produce RFC1991 signatures which use \fBMESSAGE\fR instead of \fBSIGNATURE\fR\&. +Signatures begin with an "ASCII Armor" header line and end with a tail line, which differ depending on signature type (as selected by \fBgpg\&.format\fR, see \fBgit-config\fR(1))\&. These are, for \fBgpg\&.format\fR values: +.PP +\fBgpg\fR (PGP) +.RS 4 +\fB\-\-\-\-\-BEGIN PGP SIGNATURE\-\-\-\-\-\fR +and +\fB\-\-\-\-\-END PGP SIGNATURE\-\-\-\-\-\fR\&. Or, if gpg is told to produce RFC1991 signatures, +\fB\-\-\-\-\-BEGIN PGP MESSAGE\-\-\-\-\-\fR +and +\fB\-\-\-\-\-END PGP MESSAGE\-\-\-\-\-\fR +.RE +.PP +\fBssh\fR (SSH) +.RS 4 +\fB\-\-\-\-\-BEGIN SSH SIGNATURE\-\-\-\-\-\fR +and +\fB\-\-\-\-\-END SSH SIGNATURE\-\-\-\-\-\fR +.RE +.PP +\fBx509\fR (X\&.509) +.RS 4 +\fB\-\-\-\-\-BEGIN SIGNED MESSAGE\-\-\-\-\-\fR +and +\fB\-\-\-\-\-END SIGNED MESSAGE\-\-\-\-\-\fR +.RE .sp Signatures sometimes appear as a part of the normal payload (e\&.g\&. a signed tag has the signature block appended after the payload that the signature applies to), and sometimes appear in the value of an object header (e\&.g\&. a merge commit that merged a signed tag would have the entire tag contents on its "mergetag" header)\&. In the case of the latter, the usual multi\-line formatting rule for object headers applies\&. I\&.e\&. the second and subsequent lines are prefixed with a SP to signal that the line is continued from the previous line\&. .sp |