It follows the standard URL schema for PKS/SKS systems
It implements the operations:
- 'index' : returns key index information
- 'get': returns an ASCII armored public key
- 'add': adds a key to the collection (does not update the index)
It only depends on GPG for key submission; for retrieval and searching it just looks for files in the root (eg. /var/tmp/testkeyserver). The files are named like this:
0x<keyid|fingerprint>.<operation>
Example:
$ gpg --list-key cprov > 0x681B6469.index
note: remove the lines containing 'sub' or 'secret' keys
$ gpg --export -a cprov > 0x681B6469.get
| Function | locate_key | Find a key file in the root with the given suffix. |
| Class | KeyServerResource | Root resource for the test keyserver. |
| Class | PksResource | Undocumented |
| Class | LookUp | Undocumented |
| Class | SubmitKey | Undocumented |
| Class | _BaseResource | No class docstring; 1/1 methods documented |
This does some globbing to possibly find a fingerprint-named key file when given a key ID.
| Parameters | root | The root directory in which to look. |
| suffix | The key ID or fingerprint, of the form 0x<FINGERPRINT|KEYID>.<METHOD> | |
| Returns | An absolute path to the key file. | |