1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-06-19 00:52:46 +02:00

* DETAILS: Document the --attribute-fd data.

* gpg.sgml: Document --set-notation.  Explain why it is not possible to
disable permission warnings in the gpg.conf file about the homedir.  Add
pointer in --ignore-time-conflict to see --ignore-valid from, and vice
versa.  Warning not to try and parse --list-keys in scripts. Document the
signature flags (1-3/L/R/P/N/X), Document expandos %g and %p.  Note the
default --personal-digest-preferences are "H2".
This commit is contained in:
David Shaw 2003-07-10 12:42:49 +00:00
parent df79db51f1
commit 3bc9e79103
3 changed files with 99 additions and 26 deletions

View File

@ -1,3 +1,15 @@
2003-07-10 David Shaw <dshaw@jabberwocky.com>
* DETAILS: Document the --attribute-fd data.
* gpg.sgml: Document --set-notation. Explain why it is not
possible to disable permission warnings in the gpg.conf file about
the homedir. Add pointer in --ignore-time-conflict to see
--ignore-valid from, and vice versa. Warning not to try and parse
--list-keys in scripts. Document the signature flags
(1-3/L/R/P/N/X), Document expandos %g and %p. Note the default
--personal-digest-preferences are "H2".
2003-05-26 David Shaw <dshaw@jabberwocky.com> 2003-05-26 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml, gpgv.sgml: Small SGML fixes. (From wk on stable * gpg.sgml, gpgv.sgml: Small SGML fixes. (From wk on stable

View File

@ -432,6 +432,32 @@ more arguments in future versions.
0x04 = this attribute packet is expired 0x04 = this attribute packet is expired
Format of the "--attribute-fd" output
=====================================
When --attribute-fd is set, during key listings (--list-keys,
--list-secret-keys) GnuPG dumps each attribute packet to the file
descriptor specified. --attribute-fd is intended for use with
--status-fd as part of the required information is carried on the
ATTRIBUTE status tag (see above).
The contents of the attribute data is specified by 2440bis, but for
convenience, here is the Photo ID format, as it is currently the only
attribute defined:
Byte 0-1: The length of the image header. Due to a historical
accident (i.e. oops!) back in the NAI PGP days, this is
a little-endian number. Currently 16 (0x10 0x00).
Byte 2: The image header version. Currently 0x01.
Byte 3: Encoding format. 0x01 == JPEG.
Byte 4-15: Reserved, and currently unused.
All other data after this header is raw image (JPEG) data.
Key generation Key generation
============== ==============
Key generation shows progress by printing different characters to Key generation shows progress by printing different characters to

View File

@ -216,8 +216,13 @@ B<-k> [I<username>] [I<keyring>]
<term>--list-keys &OptParmNames;</term> <term>--list-keys &OptParmNames;</term>
<term>--list-public-keys &OptParmNames;</term> <term>--list-public-keys &OptParmNames;</term>
<listitem><para> <listitem><para>
List all keys from the public keyrings, or just the List all keys from the public keyrings, or just the ones given on the
ones given on the command line. command line.
</para><para>
Avoid using the output of this command in scripts or other programs as
it is likely to change as GnuPG changes. See --with-colons for a
machine-parseable key listing command that is appropriate for use in
scripts and other programs.
</para></listitem></varlistentry> </para></listitem></varlistentry>
@ -235,6 +240,18 @@ is not usable (for example, if it was created via
<term>--list-sigs &OptParmNames;</term> <term>--list-sigs &OptParmNames;</term>
<listitem><para> <listitem><para>
Same as --list-keys, but the signatures are listed too. Same as --list-keys, but the signatures are listed too.
</para><para>
For each signature listed, there are several flags in between the
"sig" tag and keyid. These flags give additional information about
each signature. From left to right, they are the numbers 1-3 for
certificate check level (see --default-cert-check-level), "L" for a
local or non-exportable signature (see --lsign-key), "R" for a
nonRevocable signature (see --nrsign-key), "P" for a signature that
contains a policy URL (see --cert-policy-url), "N" for a signature
that contains a notation (see --cert-notation), "X" for an eXpired
signature (see --ask-cert-expire), and the numbers 1-9 or "T" for 10
and above to indicate trust signature levels (see the --edit-key
command "tsign").
</para></listitem></varlistentry> </para></listitem></varlistentry>
@ -1214,6 +1231,7 @@ photo ID attached to the key, if any. See also --photo-viewer.
<varlistentry> <varlistentry>
<term>--photo-viewer &ParmString;</term> <term>--photo-viewer &ParmString;</term>
<listitem><para> <listitem><para>
This is the command line that should be run to view a photo ID. "%i" This is the command line that should be run to view a photo ID. "%i"
will be expanded to a filename containing the photo. "%I" does the will be expanded to a filename containing the photo. "%I" does the
same, except the file will not be deleted once the viewer exits. same, except the file will not be deleted once the viewer exits.
@ -1224,7 +1242,8 @@ and "%%" for an actual percent sign. If neither %i or %I are present,
then the photo will be supplied to the viewer on standard input. then the photo will be supplied to the viewer on standard input.
</para><para> </para><para>
The default viewer is "xloadimage -fork -quiet -title 'KeyID 0x%k' The default viewer is "xloadimage -fork -quiet -title 'KeyID 0x%k'
stdin" stdin". Note that if your image viewer program is not secure, then
executing it from GnuPG does not make it secure.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
@ -1464,7 +1483,7 @@ Force inclusion of the version string in ASCII armored output.
<varlistentry> <varlistentry>
<term>--sig-notation &ParmNameValue;</term> <term>--sig-notation &ParmNameValue;</term>
<term>--cert-notation &ParmNameValue;</term> <term>--cert-notation &ParmNameValue;</term>
<term>-N, --notation-data &ParmNameValue;</term> <term>-N, --set-notation &ParmNameValue;</term>
<listitem><para> <listitem><para>
Put the name value pair into the signature as notation data. Put the name value pair into the signature as notation data.
&ParmName; must consist only of printable characters or spaces, and &ParmName; must consist only of printable characters or spaces, and
@ -1475,18 +1494,20 @@ encoded in UTF8, so you should check that your --charset is set
correctly. If you prefix &ParmName; with an exclamation mark, the correctly. If you prefix &ParmName; with an exclamation mark, the
notation data will be flagged as critical (rfc2440:5.2.3.15). notation data will be flagged as critical (rfc2440:5.2.3.15).
--sig-notation sets a notation for data signatures. --cert-notation --sig-notation sets a notation for data signatures. --cert-notation
sets a notation for key signatures (certifications). --notation-data sets a notation for key signatures (certifications). --set-notation
sets both. sets both.
</para> </para>
<para> <para>
There are special codes that may be used in notation names. "%k" will There are special codes that may be used in notation names. "%k" will
be expanded into the key ID of the key being signed, "%K" for the long be expanded into the key ID of the key being signed, "%K" into the
key ID of the key being signed, "%f" for the key fingerprint of the long key ID of the key being signed, "%f" into the fingerprint of the
key being signed, "%s" for the key ID of the key making the signature, key being signed, "%s" into the key ID of the key making the
"%S" for the long key ID of the key making the signature, and "%%" signature, "%S" into the long key ID of the key making the signature,
results in a single "%". %k, %K, and %f are only meaningful when "%g" into the fingerprint of the key making the signature (which might
making a key signature (certification). be a subkey), "%p" into the fingerprint of the primary key of the key
making the signature, and "%%" results in a single "%". %k, %K, and
%f are only meaningful when making a key signature (certification).
</para> </para>
</listitem></varlistentry> </listitem></varlistentry>
@ -1933,18 +1954,20 @@ it does not ensure the de-facto standard format of user IDs.
<term>--ignore-time-conflict</term> <term>--ignore-time-conflict</term>
<listitem><para> <listitem><para>
GnuPG normally checks that the timestamps associated with keys and GnuPG normally checks that the timestamps associated with keys and
signatures have plausible values. However, sometimes a signature seems to signatures have plausible values. However, sometimes a signature
be older than the key due to clock problems. This option makes these seems to be older than the key due to clock problems. This option
checks just a warning. makes these checks just a warning. See also --ignore-valid-from for
timestamp issues on subkeys.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
<term>--ignore-valid-from</term> <term>--ignore-valid-from</term>
<listitem><para> <listitem><para>
GnuPG normally does not select and use subkeys created in the future. This GnuPG normally does not select and use subkeys created in the future.
option allows the use of such keys and thus exhibits the pre-1.0.7 This option allows the use of such keys and thus exhibits the
behaviour. You should not use this option unless you there is some pre-1.0.7 behaviour. You should not use this option unless you there
clock problem. is some clock problem. See also --ignore-time-conflict for timestamp
issues with signatures.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
@ -2023,11 +2046,18 @@ Suppress the warning about "using insecure memory".
<varlistentry> <varlistentry>
<term>--no-permission-warning</term> <term>--no-permission-warning</term>
<listitem><para> <listitem><para>
Suppress the warning about unsafe file permissions. Note that the
file permission checks that GnuPG performs are not intended to be Suppress the warning about unsafe file and home directory (--homedir)
authoritative, rather they simply warn about certain common permission permissions. Note that the permission checks that GnuPG performs are
problems. Do not assume that the lack of a warning means that your not intended to be authoritative, but rather they simply warn about
system is secure. certain common permission problems. Do not assume that the lack of a
warning means that your system is secure.
</para><para>
Note that the warning for unsafe --homedir permissions cannot be
supressed in the gpg.conf file, as this would allow an attacker to
place an unsafe gpg.conf file in place, and use this file to supress
warnings about itself. The --homedir permissions warning may only be
supressed on the command line.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
@ -2064,8 +2094,12 @@ verification is not needed.
<varlistentry> <varlistentry>
<term>--with-colons</term> <term>--with-colons</term>
<listitem><para> <listitem><para>
Print key listings delimited by colons. Note, that the output will be Print key listings delimited by colons. Note that the output will be
encoded in UTF-8 regardless of any --charset setting. encoded in UTF-8 regardless of any --charset setting. This format is
useful when GnuPG is called from scripts and other programs as it is
easily machine parsed. The details of this format are documented in
the file doc/DETAILS, which is included in the GnuPG source
distribution.
</para></listitem></varlistentry> </para></listitem></varlistentry>
@ -2260,7 +2294,8 @@ should be a string similar to the one printed by the command "pref" in
the edit menu. This allows the user to factor in their own preferred the edit menu. This allows the user to factor in their own preferred
algorithms when algorithms are chosen via recipient key preferences. algorithms when algorithms are chosen via recipient key preferences.
The most highly ranked digest algorithm in this list is algo used when The most highly ranked digest algorithm in this list is algo used when
signing without encryption (e.g. --clearsign or --sign). signing without encryption (e.g. --clearsign or --sign). The default
value is "H2" indicating SHA-1.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>