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

gpg: Allow use of a standard space separated fingerprint.

Browse source 
* common/userids.c (classify_user_id): Check for space separated GPG
fingerprint.
This commit is contained in:
Werner Koch 2012-01-06 13:33:10 +01:00
parent 5988c8bfb7
commit 372fb4fc06
3 changed files with 48 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -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 <heinrichh@@uni-duesseldorf.de>
@end example
@end cartouche