security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-22 14:57:02 +01:00
Code Activity

manual fixes and some hints for the forthcoming gpgsm in DETAILS

Browse Source
This commit is contained in:
Werner Koch 2001-12-15 18:25:55 +00:00
parent c42da770ea
commit 0f47bb3c19
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/DETAILS
View File

@ -7,6 +7,7 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
1. Field: Type of record
pub = public key
crt = X.509 certificate
sub = subkey (secondary key)
sec = secret key
ssb = secret subkey (secondary key)
@ -14,6 +15,8 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
sig = signature
fpr = fingerprint: (fingerprint is in field 10)
pkd = public key data (special field format, see below)
grp = reserved for gpgsm
2. Field: A letter describing the calculated trust. This is a single
letter, but be prepared that additional information may follow
@ -38,12 +41,14 @@ ssb::1536:20:5CE086B5B5A18FF4:1998-07-07:0:::
5. Field: KeyID
6. Field: Creation Date (in UTC)
7. Field: Key expiration date or empty if none.
8. Field: reserved (used to be the Local-ID)
8. Field: Used for serial number in crt records (used to be the Local-ID)
9. Field: Ownertrust (primary public keys only)
This is a single letter, but be prepared that additional
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").
This is not used with --fixed-list-mode in gpg.
In gpgsm the issuer name does here
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.

4
doc/gpg.texi
View File

@ -792,8 +792,8 @@ signatures on data.
Reset the ---force-v3-sigs option.
@item ---force-v4-certs
Always use v4 key signatures even on v3 version keys. This make the
signature unusable for PGP 2.
Always use v4 key signatures even on v3 keys. This option does also
change the default hash algorithm for v3 RSA keys from MD5 to SHA-1.
@item ---no-force-v3-certs
Reset the ---force-v4-certs option.