Changes

Jump to: navigation, search

NSS Shared DB

7 bytes removed, 00:47, 5 February 2008
Shared Database Proposal
== Shared Database Proposal ==
NSS has been using an old version of the Berkeley DataBase as its database engine since Netscape Navigator 2.0 in 1994. That version of the This database engine is commonly described in NSS documents as "DBM". That engine and has a
number of limitations. One of the most severe limitations concerns the
number of processes that may share a database file. While any process has
own shared database implementation, and configured NSS to use it.
Today, there exists a process level, ACID, open source, and widely available database engine with which multiple processes may simultaneous have read and write access to a shared database. It is named SQLite. The NSS team proposes to leverage use this database to give all NSS-based applications Shared Database access.
Besides the inability to share databases, other issues with NSS DBM database scheme include:
Also in that directory:<br />
* If it has very large security objects (such as large CRLs), NSS will store them in files in a subdirectory named cert8.dir.
* If the cert8.db and/or key3.db files are missing, NSS will read data from older versions of those databases (e.g., cert7.db, cert5.db, if they exist) and may build new cert8.db and/or key3.db fileswith that data (upgrade).
These files are all accessed exclusively by the softoken shared library, making it the only NSS library that must be linked with libdbm.
439
edits

Navigation menu