NSS Shared DB: Difference between revisions

Jump to navigation Jump to search
m (fix one numbered list)
Line 1: Line 1:
== Shared Database Proposal ==
== Shared Database Proposal ==


Applications have been chaffing at the restrictions of the current NSS database for quite some time now. In 2001 we built some tools to work around those restrictions so certain applications could share the database if they supplied their own shared database implementation, and configured NSS to use that implementation. Today we have a process level, ACID, open source, and widely available database called SQLite. In addition, there is a strong desire to make NSS the system security service for Linux. I am proposing how we could leverage this database to give all of our applications Shared Database access.
Some application developers using NSS have complained about the NSS database scheme. In particular, they have pointed out that they cannot share a single NSS certificate and key database between applications. (ARE THERE OTHER ISSUES? SPELL THEM OUT.)
 
In 2001 we built some tools to work around those restrictions so certain applications could share the database if they supplied their own shared database implementation, and configured NSS to use that implementation. Today we have a process level, ACID, open source, and widely available database called SQLite. In addition, there is a strong desire to make NSS the system security service for Linux. I am proposing how we could leverage this database to give all of our applications Shared Database access.


=== Where we are today ===
=== Where we are today ===
118

edits

Navigation menu