From 372fb4fc0661014ccd9275c89e6da2208f87155f Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Fri, 6 Jan 2012 13:33:10 +0100 Subject: gpg: Allow use of a standard space separated fingerprint. * common/userids.c (classify_user_id): Check for space separated GPG fingerprint. --- doc/specify-user-id.texi | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/specify-user-id.texi b/doc/specify-user-id.texi index 7d23ed86f..2eee0245a 100644 --- a/doc/specify-user-id.texi +++ b/doc/specify-user-id.texi @@ -6,7 +6,7 @@ are only valid for @command{gpg} others are only good for @itemize @bullet -@item By key Id. +@item By key Id. This format is deduced from the length of the string and its content or @code{0x} prefix. The key Id of an X.509 certificate are the low 64 bits of its SHA-1 fingerprint. The use of key Ids is just a shortcut, for @@ -59,16 +59,17 @@ avoids any ambiguities in case that there are duplicated key IDs. @end cartouche @noindent -(@command{gpgsm} also accepts colons between each pair of hexadecimal +@command{gpgsm} also accepts colons between each pair of hexadecimal digits because this is the de-facto standard on how to present X.509 -fingerprints.) +fingerprints. @command{gpg} also allows the use of the space +separated SHA-1 fingerprint as printed by the key listing commands. @item By exact match on OpenPGP user ID. This is denoted by a leading equal sign. It does not make sense for X.509 certificates. @cartouche -@example +@example =Heinrich Heine @end example @end cartouche -- cgit v1.2.3