Changes between Initial Version and Version 1 of CryptoPlugin/Dev/DbSchema


Ignore:
Timestamp:
Jun 25, 2012, 7:41:05 PM (12 years ago)
Author:
Steffen Hoffmann
Comment:

initial content taken from local development wiki

Legend:

Unmodified
Added
Removed
Modified
  • CryptoPlugin/Dev/DbSchema

    v1 v1  
     1= Db storage organization for CryptoPlugin =
     2Right now I can think of only two requirements for plugin-specific information:
     3 * user <--> key associations
     4 * (detached) signature storage
     5
     6== Common "parasite" storage ==
     7Entries in `session_attribute` seem like a perfect match for the first requirement.
     8I've chosen the following dedicated names for related association types:
     9 * 'sign_key'
     10 * 'crypt_key'
     11 * 'auth_key' (''future'')
     12
     13== Dedicated "private" storage ==
     14For storing signature data we could resort to inline signed data, but I felt that this choice would restrict possible use cases too much.
     15So I chose detached signatures as the default. Resources stay unaltered by signing, and you will be able to sign text content as well as arbitrary binary/file data.
     16
     17After 3 internal iterations current db schema draft is like so:
     18{{{
     19table `crypto_sign`
     20  * realm,
     21  * id,
     22  * version,
     23  * fragment,
     24 i* key_id,
     25    signature
     26 i  time,
     27
     28 * primary key
     29 i has dedicated index:
     30}}}
     31
     32Discussion welcome.