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

just released another snapshot

Browse source
This commit is contained in:
Werner Koch 2001-05-28 12:46:28 +00:00
parent ca284c1000
commit e354b518d3
46 changed files with 1033 additions and 5130 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/DETAILS
View file

@ -11,6 +11,7 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
sec = secret key
ssb = secret subkey (secondary key)
uid = user id (only field 10 is used).
sig = signature
fpr = fingerprint: (fingerprint is in field 10)
pkd = public key data (special field format, see below)
@ -47,7 +48,9 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
information may follow in some future versions.
10. Field: User-ID. The value is quoted like a C string to avoid
control characters (the colon is quoted "\x3a").
11. Field: Signature class
11. Field: Signature class. This is a 2 digit hexnumber followed by
either the letter 'x' for an exportable signature or the
letter 'l' for a local-only signature.
12. Field: Key capabilities:
e = encrypt
s = sign
@ -56,9 +59,12 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
addition to these letters, uppercase version of the letter to
denote the _usable_ capabilities of the entire key.
All dates are displayed in the format yyyy-mm-dd unless you use the option
--fixed-list-mode in which case they are dispplay as seconds since epoch.
More fields may be added later.
All dates are displayed in the format yyyy-mm-dd unless you use the
option --fixed-list-mode in which case they are displayed as seconds
since Epoch. More fields may be added later, so parsers should be
prepared for this. When parsing a number the parser should stop at the
first non-number character so that additional information can later be
added.
If field 1 has the tag "pkd", a listing looks like this:
pkd:0:1024:B665B1435F4C2 .... FF26ABB: