Pubkey Database

Freedom Services 2.0 Archive Validated

$Author: alext $
$Date: 2001/07/24 20:01:10 $
$Revision: 1.9 $

Overview

The Pubkey Database holds public keys for all entities on the freedom network. The Key Query Daemon serves the contents of this database. There is a secondary Pubkey database which holds backups of keys for entities which have been nuked from the network. Currently only nuked and deleted nyms are stored in the backup database. Both databases have the same format and share most access information.

Access

Always use the supplied library to access the database. If the required functionality is not there, then extend the library. The pubkey databases are accessible through a database server, so you should use the remote config file.
Understanding database configuration.

(NB: "xxx" is either "local" or "remote")

Regular or Nuked

A secondary nuked database is used to store backups of keys for nyms which have been nuked or deleted using the administrative lode server. These keys do not appear in the main database.

Info

Details

With the exception of a duplicate record corresponding to an entity's current key, the database consists of a single record for each public key. The entries are uniquely identified by the tuple <key-version, key-type, key-owner>, where key-type refers to signing or encryption and the key-owner corresponds to the ent field of the key. To ask for the current key, key-version is set to 0.

The public key database datum is the public key data, in the format described above, with a little extra information. This is the entity who signs the entry and their signature. The signature is over the entire datum. Cryption keys are signed by that same entity's signing key, while signature keys are signed by the entity's parent in the key hierarchy.