diff --git a/doc/ChangeLog b/doc/ChangeLog index b7dc01eb8..05366c345 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,15 @@ +2003-07-10 David Shaw + + * 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 * gpg.sgml, gpgv.sgml: Small SGML fixes. (From wk on stable diff --git a/doc/DETAILS b/doc/DETAILS index ad7c60942..c00914bb7 100644 --- a/doc/DETAILS +++ b/doc/DETAILS @@ -432,6 +432,32 @@ more arguments in future versions. 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 shows progress by printing different characters to diff --git a/doc/gpg.sgml b/doc/gpg.sgml index cf35d4d62..928a7a504 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -216,8 +216,13 @@ B<-k> [I] [I] --list-keys &OptParmNames; --list-public-keys &OptParmNames; -List all keys from the public keyrings, or just the -ones given on the command line. +List all keys from the public keyrings, or just the ones given on the +command line. + +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. @@ -235,6 +240,18 @@ is not usable (for example, if it was created via --list-sigs &OptParmNames; Same as --list-keys, but the signatures are listed too. + +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"). @@ -1214,6 +1231,7 @@ photo ID attached to the key, if any. See also --photo-viewer. --photo-viewer &ParmString; + 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 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. 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. @@ -1464,7 +1483,7 @@ Force inclusion of the version string in ASCII armored output. --sig-notation &ParmNameValue; --cert-notation &ParmNameValue; --N, --notation-data &ParmNameValue; +-N, --set-notation &ParmNameValue; Put the name value pair into the signature as notation data. &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 notation data will be flagged as critical (rfc2440:5.2.3.15). --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. 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 -key ID of the key being signed, "%f" for the key fingerprint of the -key being signed, "%s" for the key ID of the key making the signature, -"%S" for the long key ID of the key making the signature, and "%%" -results in a single "%". %k, %K, and %f are only meaningful when -making a key signature (certification). +be expanded into the key ID of the key being signed, "%K" into the +long key ID of the key being signed, "%f" into the fingerprint of the +key being signed, "%s" into the key ID of the key making the +signature, "%S" into the long key ID of the key making the signature, +"%g" into the fingerprint of the key making the signature (which might +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). @@ -1933,18 +1954,20 @@ it does not ensure the de-facto standard format of user IDs. --ignore-time-conflict GnuPG normally checks that the timestamps associated with keys and -signatures have plausible values. However, sometimes a signature seems to -be older than the key due to clock problems. This option makes these -checks just a warning. +signatures have plausible values. However, sometimes a signature +seems to be older than the key due to clock problems. This option +makes these checks just a warning. See also --ignore-valid-from for +timestamp issues on subkeys. --ignore-valid-from -GnuPG normally does not select and use subkeys created in the future. This -option allows the use of such keys and thus exhibits the pre-1.0.7 -behaviour. You should not use this option unless you there is some -clock problem. +GnuPG normally does not select and use subkeys created in the future. +This option allows the use of such keys and thus exhibits the +pre-1.0.7 behaviour. You should not use this option unless you there +is some clock problem. See also --ignore-time-conflict for timestamp +issues with signatures. @@ -2023,11 +2046,18 @@ Suppress the warning about "using insecure memory". --no-permission-warning -Suppress the warning about unsafe file permissions. Note that the -file permission checks that GnuPG performs are not intended to be -authoritative, rather they simply warn about certain common permission -problems. Do not assume that the lack of a warning means that your -system is secure. + +Suppress the warning about unsafe file and home directory (--homedir) +permissions. Note that the permission checks that GnuPG performs are +not intended to be authoritative, but rather they simply warn about +certain common permission problems. Do not assume that the lack of a +warning means that your system is secure. + +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. @@ -2064,8 +2094,12 @@ verification is not needed. --with-colons -Print key listings delimited by colons. Note, that the output will be -encoded in UTF-8 regardless of any --charset setting. +Print key listings delimited by colons. Note that the output will be +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. @@ -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 algorithms when algorithms are chosen via recipient key preferences. 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.