diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/FAQ | 14 | ||||
| -rw-r--r-- | doc/gpg.sgml | 95 |
3 files changed, 110 insertions, 3 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index 61e3ff2fc..91e3f273b 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +Sat Dec 4 12:30:28 CET 1999 Werner Koch <[email protected]> + + * gpg.sgml: Add section about the user ID + Mon Nov 22 11:14:53 CET 1999 Werner Koch <[email protected]> * gph: Removed the directory from the dist becuase it will @@ -346,10 +346,10 @@ material? A: No. For example you can add or remove "Comment:" lines. They have a purpose like the mail header lines. However a "Hash:" - line is needed for modern signatures, to tell the parser which + line is needed for OpenPGG signatures to tell the parser which hash algorithm to use. - Q: Now can a get list of key IDs used to encrypt a message? + Q: How can a get list of key IDs used to encrypt a message? A: gpg --batch --decrypt --status-fd 1 2>/dev/null \ | awk '/^\[GNUPG:\] ENC_TO / { print $3 }' @@ -357,9 +357,17 @@ Q: PGP 5.x, 6.x does not like my secret key. A: PGP probaly bails out on some private comment packets used by GnuPG. These packets are fully in compliance with OpenPGP; however PGP is not - really OPenPGP aware. A workaround is to eport the secret keys with + really OpenPGP aware. A workaround is to eport the secret keys with this command: gpg --export-secret-keys --no-comment -a your-key-id + Q: I can't decrypt my symmetrical only (-c) encrypted message with + a new version of GnuPG. + A: There used to be a bug in GnuPG < 1.0.1 which happens only if 3DES + was used for symmetric only encryption (this has never been the default). + The bug has been fixed but to enable you to decrypt old messages, you + should run gpg with the option "--emulate-3des-s2k-bug", decrypt the + message and encrypt it again without this option. The option will + be removed in 1.1, so better re/encrypt your message now. diff --git a/doc/gpg.sgml b/doc/gpg.sgml index 52d9773ac..3415b23c6 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -1248,6 +1248,101 @@ This is not for normal use. Use the source to see for what it might be useful. </variablelist> </refsect1> + +<refsect1> + <title>How to specify a user ID</title> + <para> +There are different ways on how to specify a user ID to GnuPG; +here are some examples: + </para> + + <variablelist> +<varlistentry> +<term></term> +<listitem><para>Used to locate the default home directory.</para></listitem> +</varlistentry> + +<varlistentry> +<term>234567C4</term> +<term>0F34E556E</term> +<term>01347A56A</term> +<term>0xAB123456</term> +<listitem><para> +Here the key ID is given in the usual short form. +</para></listitem> +</varlistentry> + +<varlistentry> +<term>234AABBCC34567C4</term> +<term>0F323456784E56EAB</term> +<term>01AB3FED1347A5612</term> +<term>0x234AABBCC34567C4</term> +<listitem><para> +Here the key ID is given in the long form as used by OpenPGP. +</para></listitem> +</varlistentry> + +<varlistentry> +<term>1234343434343434C434343434343434</term> +<term>123434343434343C3434343434343734349A3434</term> +<term>0E12343434343434343434EAB3484343434343434</term> +<term>0xE12343434343434343434EAB3484343434343434</term> +<listitem><para> +The best way to specify a key ID is by using the fingerprint of +the key. This avoids any ambiguities in case that there are duplicated +kez IDs (which are really rare for the long key IDs). +</para></listitem> +</varlistentry> + +<varlistentry> +<term>=Heinrich Heine <[email protected]></term> +<listitem><para> +Using an exact to match string. The equal sign indicates this. +</para></listitem> +</varlistentry> + +<varlistentry> +<term><[email protected]></term> +<listitem><para> +Using the email address part which must match exactly. The left angle bracket +indicates this email address mode. +</para></listitem> +</varlistentry> + +<varlistentry> +<term>+Heinrich Heine duesseldorf</term> +<listitem><para> +All words must match exactly (not case sensitive) but can appear in +any order in the user ID. Words are any sequences of letters, +digits, the underscore and all characters with bit 7 set. +</para></listitem> +</varlistentry> + +<varlistentry> +<term>#34</term> +<listitem><para> +Using the Local ID. This is a very low level method and should +only be used by applications which really need it. The hash character +indicates this method. An application should not assume that this is +only a number. +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Heine</term> +<term>*Heine</term> +<listitem><para> +By case insensitive substring matching. This is the default mode but +applications maz want to explicitely indicate this bz putting the asterisk +in front. +</para></listitem> +</varlistentry> + + </variablelist> + +</refsect1> + + <refsect1> <title>RETURN VALUE</title> <para> |