See ChangeLog: Sat Mar 20 13:59:47 CET 1999 Werner Koch

doc/DETAILS

@@ -155,12 +155,12 @@ describes the record type.  All numeric values are stored in network
 byte order. The length of each record is 40 bytes. The first record of
 the DB is always of type 2 and this is the only record of this type.
 
-Record type 0:
---------------
+  Record type 0:
+  --------------
     Unused record, can be reused for any purpose.
 
-Record type 1:
---------------
+  Record type 1:
+  --------------
     Version information for this TrustDB.  This is always the first
     record of the DB and the only one with type 1.
      1 byte value 1
@@ -187,8 +187,8 @@ Record type 1:
      4 bytes reserved for version extension record
 
 
-Record type 2: (directory record)
---------------
+  Record type 2: (directory record)
+  --------------
     Informations about a public key certificate.
     These are static values which are never changed without user interaction.
 
@@ -205,8 +205,8 @@ Record type 2: (directory record)
     15 byte reserved
 
 
-Record type 3:	(key record)
---------------
+  Record type 3:  (key record)
+  --------------
     Informations about a primary public key.
     (This is mainly used to lookup a trust record)
 
@@ -221,8 +221,8 @@ Record type 3:	(key record)
      20 bytes fingerprint of the public key
 	      (This is the value we use to identify a key)
 
-Record type 4: (uid record)
---------------
+  Record type 4: (uid record)
+  --------------
     Informations about a userid
     We do not store the userid but the hash value of the userid because that
     is sufficient.
@@ -238,8 +238,8 @@ Record type 4: (uid record)
      20 bytes ripemd160 hash of the username.
 
 
-Record type 5: (pref record)
---------------
+  Record type 5: (pref record)
+  --------------
     Informations about preferences
 
      1 byte value 5
@@ -249,8 +249,8 @@ Record type 5: (pref record)
      1 u32  next
      30 byte preference data
 
-Record type 6  (sigrec)
--------------
+  Record type 6  (sigrec)
+  -------------
     Used to keep track of key signatures. Self-signatures are not
     stored.  If a public key is not in the DB, the signature points to
     a shadow dir record, which in turn has a list of records which
@@ -270,8 +270,8 @@ Record type 6  (sigrec)
 
 
 
-Record type 8: (shadow directory record)
---------------
+  Record type 8: (shadow directory record)
+  --------------
     This record is used to reserved a LID for a public key.  We
     need this to create the sig records of other keys, even if we
     do not yet have the public key of the signature.
@@ -294,8 +294,8 @@ Record type 8: (shadow directory record)
 
 
 
-Record Type 10 (hash table)
---------------
+  Record Type 10 (hash table)
+  --------------
     Due to the fact that we use fingerprints to lookup keys, we can
     implement quick access by some simple hash methods, and avoid
     the overhead of gdbm.  A property of fingerprints is that they can be
@@ -332,8 +332,8 @@ Record Type 10 (hash table)
 	 fingerprint and to decide whether it is the requested key;
 
 
-Record type 11 (hash list)
---------------
+  Record type 11 (hash list)
+  --------------
     see hash table for an explanation.
     This is also used for other purposes.
 
@@ -347,8 +347,8 @@ Record type 11 (hash list)
 
 
 
-Record type 254 (free record)
----------------
+  Record type 254 (free record)
+  ---------------
     All these records form a linked list of unused records.
      1 byte  value 254
      1 byte  reserved (0)
@@ -452,17 +452,17 @@ Other Notes
 
 
 Keyserver Message Format
--------------------------
+=========================
 
 The keyserver may be contacted by a Unix Domain socket or via TCP.
 
 The format of a request is:
 
-----
+====
 command-tag
 "Content-length:" digits
 CRLF
-------
+=======
 
 Where command-tag is
 
@@ -474,11 +474,11 @@ DELETE <user-name>
 
 The format of a response is:
 
-------
+======
 "GNUPG/1.0" status-code status-text
 "Content-length:" digits
 CRLF
-------------
+============
 followed by <digits> bytes of data