118
edits
| Line 53: | Line 53: | ||
=== SQLite-Based Multiaccess Certificate and Key Databases === | === SQLite-Based Multiaccess Certificate and Key Databases === | ||
Many client applications, such as Mozilla Firefox, Mozilla Thunderbird, Evolution, OpenOffice.org, are using NSS now, but they each have their own certificate and key databases. As a result, if you import and trust a certificate in Firefox, you will not see it in Thunderbird. This is because Berkeley DB 1.85, the database NSS currently | Many client applications, such as Mozilla Firefox, Mozilla Thunderbird, Evolution, OpenOffice.org, are using NSS now, but they each have their own certificate and key databases. As a result, for example, if you import and trust a certificate in Firefox, you will not see it in Thunderbird. This is because Berkeley DB 1.85, the database NSS currently uses, can't be used by multiple processes. | ||
Although new versions of Berkeley DB (from Sleepycat Software) support multiprocess access, its open source license is incompatible with the Mozilla Public License (MPL). | Although new versions of Berkeley DB (from Sleepycat Software) support multiprocess access, its open source license is incompatible with the Mozilla Public License (MPL). | ||
We are planning to implement a multiaccess database using the public-domain SQLite. In NSS 3.11 we plan to offer this new multiaccess database as an alternate database plugin (librdb.so). We plan to make it the default database in NSS 3.12. | We are planning to implement a multiaccess database using the public-domain SQLite. In NSS 3.11 we plan to offer this new multiaccess database as an alternate database plugin (librdb.so). We plan to make it the default database in NSS 3.12. Other Mozilla teams are adopting SQLite, making it a logical choice for the NSS project as well. | ||
<b>Note:</b> because this change will affect code inside the FIPS 140-2 defined module boundaries, we will need to document these changes and obtain a delta validation. | <b>Note:</b> because this change will affect code inside the FIPS 140-2 defined module boundaries, we will need to document these changes and obtain a delta validation. | ||
edits