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

doc: Add comments on how to parse --list-colons output.

Browse source 
--

GnuPG-bug-id: 2437
This commit is contained in:
Werner Koch 2016-08-18 12:41:55 +02:00
parent d83ba4897b
commit d25db3c903
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
2 changed files with 12 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/DETAILS
View file

@ -31,11 +31,18 @@ sub:r:1536:20:5CE086B5B5A18FF4:899817788:1025961788:::::esc:
fpr:::::::::AB059359A3B81F410FCFF97F5CE086B5B5A18FF4:
#+end_example
Note that new version of GnuPG or the use of certain options may add
new fields to the output. Parsers should not assume a limit on the
number of fields per line. Some fields are not yet used or only used
with certain record types; parsers should ignore fields they are not
aware of.
The double =--with-fingerprint= prints the fingerprint for the subkeys
too. Old versions of gpg used a slightly different format and required
the use of the option =--fixed-list-mode= to conform to the format
described here.
** Description of the fields
*** Field 1 - Type of record
@ -337,8 +344,8 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
Every line is prefixed with "[GNUPG:] ", followed by a keyword with
the type of the status line and some arguments depending on the type
(maybe none); an application should always be prepared to see more
arguments in future versions.
(maybe none); an application should always be prepared to see new
keyworkds or more arguments in future versions.
** General status codes
*** NEWSIG [<signers_uid>]