security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

* gpg.texi, specify-user-id.texi: Only some of the mentions of

Browse source 
exclamation marks have an example.  Give examples to the rest.
This commit is contained in:
David Shaw 2007-01-18 18:52:24 +00:00
parent 1d4b3d7c3b
commit 09bc5abc92
3 changed files with 11 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/specify-user-id.texi
View file

@ -12,8 +12,8 @@ This format is deduced from the length of the string and its content or
of its SHA-1 fingerprint. The use of key Ids is just a shortcut, for
all automated processing the fingerprint should be used.
When using @command{gpg} an exclamation mark may be appended to force
using the specified primary or secondary key and not to try and
When using @command{gpg} an exclamation mark (!) may be appended to
force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The last four lines of the example give the key ID in their long form as
@ -42,8 +42,8 @@ the @code{0x} prefix. Note, that only the 20 byte version fingerprint
is available with @command{gpgsm} (i.e. the SHA-1 hash of the
certificate).
When using @command{gpg} an exclamation mark may be appended to force
using the specified primary or secondary key and not to try and
When using @command{gpg} an exclamation mark (!) may be appended to
force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The best way to specify a key Id is by using the fingerprint. This