1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-09-22 15:11:41 +02:00

* DETAILS: Removed paragraph on gdbm usage. Notes that pipemode

is deprecated.
This commit is contained in:
Werner Koch 2003-08-23 07:50:54 +00:00
parent b760ade21d
commit fd4be49da8
2 changed files with 8 additions and 23 deletions

View File

@ -1,3 +1,8 @@
2003-08-23 Werner Koch <wk@gnupg.org>
* DETAILS: Removed paragraph on gdbm usage. Notes that pipemode
is deprecated.
2003-08-21 Werner Koch <wk@gnupg.org>
* samplekeys.asc: Refreshed the keys.

View File

@ -890,33 +890,13 @@ After the hash algorithm the 3 bytes "GNU" are used to make
clear that these are extensions for GNU, the next bytes gives the
GNU protection mode - 1000. Defined modes are:
1001 - do not store the secret part at all
Usage of gdbm files for keyrings
================================
The key to store the keyblock is its fingerprint, other records
are used for secondary keys. Fingerprints are always 20 bytes
where 16 bit fingerprints are appended with zero.
The first byte of the key gives some information on the type of the
key.
1 = key is a 20 bit fingerprint (16 bytes fpr are padded with zeroes)
data is the keyblock
2 = key is the complete 8 byte keyid
data is a list of 20 byte fingerprints
3 = key is the short 4 byte keyid
data is a list of 20 byte fingerprints
4 = key is the email address
data is a list of 20 byte fingerprints
Data is prepended with a type byte:
1 = keyblock
2 = list of 20 byte padded fingerprints
3 = list of list fingerprints (but how to we key them?)
1002 - a stub to access smartcards (not used in 1.2.x)
Pipemode
========
NOTE: This is deprecated and will be removed in future versions.
This mode can be used to perform multiple operations with one call to
gpg. It comes handy in cases where you have to verify a lot of
signatures. Currently we support only detached signatures. This mode