439
edits
NSS Shared DB: Difference between revisions
Jump to navigation
Jump to search
→schema
(→schema) |
(→schema) |
||
| Line 59: | Line 59: | ||
Softoken will be able to store the following objects and attributes. In the table below, attributes marked CK_ULONG will be written to the database as a 32-bit network order unsigned integer, attributes marked 'encrypted' will be encrypted with the token's pbe key, and attributes marked 'MACed' will be MACed with the token's pbe key. | Softoken will be able to store the following objects and attributes. In the table below, attributes marked CK_ULONG will be written to the database as a 32-bit network order unsigned integer, attributes marked 'encrypted' will be encrypted with the token's pbe key, and attributes marked 'MACed' will be MACed with the token's pbe key. | ||
===== Legal Attributes and objects ===== | |||
While the key and certificate database format is extensible, the initial implementation has to understand a particular subset of attributes. The following list the attributes and understood, and any special coding conditions for that given attribute. | |||
*Stored in the key database: | *Stored in the key database: | ||
| Line 151: | Line 154: | ||
***CKA_ISSUER | ***CKA_ISSUER | ||
***CKA_SERIAL_NUMBER | ***CKA_SERIAL_NUMBER | ||
***CKA_NSS_OVERRIDE_EXTENSIONS (sql database only) - MACed | |||
**CKO_NSS_TRUST | **CKO_NSS_TRUST | ||
***CKA_CLASS - CK_ULONG | ***CKA_CLASS - CK_ULONG | ||
| Line 186: | Line 190: | ||
***CKA_NETSCAPE_SMIME_TIMESTAMP | ***CKA_NETSCAPE_SMIME_TIMESTAMP | ||
***CKA_VALUE | ***CKA_VALUE | ||
===== Special coding for CK_LONG ===== | |||
===== Special coding for encrypted entries ===== | |||
===== Special coding for MACed entries ===== | |||
==== Accessing the shared Database ==== | ==== Accessing the shared Database ==== | ||