Emaldonado (talk | contribs) |
Emaldonado (talk | contribs) |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
The softoken cryptographic module of NSS should be split off as the nss-softokn package. The utilities library which is a common library required by softokn and the rest of nss | The softoken cryptographic module of NSS should be split off as the nss-softokn package. The utilities library which is a common library required by softokn and the rest of nss should also be packaged separately as nss-utils. | ||
== Owner == | == Owner == | ||
| Line 15: | Line 15: | ||
== Detailed Description == | == Detailed Description == | ||
The softoken cryptographic module of NSS | The softoken cryptographic module of NSS needs to be packages on its own as the nss-softkn pacakage. as a consequence a set of utilities called by both the new softoken and the rest of NSS would also need to be packaged as its own package. | ||
NSS is FIPS 140 validated but what is really submitted for FIPS validation is the cryptographic module, that is, | NSS is FIPS 140 validated but what is really submitted for FIPS 140 validation is the cryptographic module sunset, that is, that is the softken PKCS #module. This split will enable users as well as package maintainers to upgrade to the current version of NSS while preserving the last FIPS validated version of the cryptographic module if they so require. Fedora based distributions such as RHEL would greatly benefit from this feature in terms of easier long term maintenance. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 25: | Line 25: | ||
This will not affect developers as it is a packaging change only and no changes to the NSS API are required nor changes to their build systems. The same libraries are shipped as before. They just get distributed among three packages. | This will not affect developers as it is a packaging change only and no changes to the NSS API are required nor changes to their build systems. The same libraries are shipped as before. They just get distributed among three packages. | ||
The nss shared libraries which are currently distributed as | The nss shared libraries which are currently distributed as: | ||
nss: libnss3.so, libnssutil3.so, libnssdbm3.so, libssl3.so, | nss: libnss3.so, libnssutil3.so, libnssdbm3.so, libssl3.so, | ||
libsmime3.so, libsoftokn3.so, libsoftokn3.chk, libnssckbi.so, libnsspem.so | libsmime3.so, libsoftokn3.so, libsoftokn3.chk, libnssckbi.so, libnsspem.so | ||
would be distributed among the packages as | nss-softokn-freebl: libfreebl3.so, libfreebl3.chk (subpackage of nss) | ||
would be distributed among the packages as: | |||
nss: libnss3.so, libnssdbm3.so, libssl3.so, libsmime3.so, libnssckbi.so, libnsspem.so | nss: libnss3.so, libnssdbm3.so, libssl3.so, libsmime3.so, libnssckbi.so, libnsspem.so | ||
softokn: libsoftokn3.so, libsoftokn3.chk | |||
softokn-freebl: libfreebl3.so, libfreebl3.chk (subpackage of softokn) | nss-softokn: libsoftokn3.so, libsoftokn3.chk | ||
util: | |||
nss-softokn-freebl: libfreebl3.so, libfreebl3.chk (subpackage of softokn) | |||
nss-util: libnssutil3.so | |||
Currently nss has a subpackage nss-devel with the headers and development libraries that will get distributed among the new packages. nss-softoken aND nss-util own development subpacakegs will install the portion of the headers of relevamce to them. Each becomes the "owner" of its share of the headers. They will be installed in the same location as before the split so as to make this change transparent to existing client packages. | |||
== How To Test == | == How To Test == | ||
| Line 43: | Line 51: | ||
There should be no regressions for components that depend on NSS. | There should be no regressions for components that depend on NSS. | ||
Examples of these are glibc, mod_nss, nss_compat_nss, crypto-utils, openswan, xulrunner, evolution, and Pidgin's libpurple. | Examples of these are glibc, mod_nss, nss_compat_nss, crypto-utils, openswan, xulrunner, evolution, and Pidgin's libpurple. | ||
== Building NSS : pre-flight and test == | |||
For a description on how to perform and test major nss updates see | |||
https://fedoraproject.org/wiki/Updating_NSS#Updating_NSS | |||
The above applies to Fedora and RHEL-6 and above. | |||
== User Experience == | == User Experience == | ||
Latest revision as of 15:57, 3 September 2014
Feature Name
Split Softoken off from NSS
Summary
The softoken cryptographic module of NSS should be split off as the nss-softokn package. The utilities library which is a common library required by softokn and the rest of nss should also be packaged separately as nss-utils.
Owner
- Name: emaldonado
- email: emaldona@redhat.com
Current status
- Targeted release: Fedora 12
- Last updated: 2009-0726
- Percentage of completion: 100%
Detailed Description
The softoken cryptographic module of NSS needs to be packages on its own as the nss-softkn pacakage. as a consequence a set of utilities called by both the new softoken and the rest of NSS would also need to be packaged as its own package.
NSS is FIPS 140 validated but what is really submitted for FIPS 140 validation is the cryptographic module sunset, that is, that is the softken PKCS #module. This split will enable users as well as package maintainers to upgrade to the current version of NSS while preserving the last FIPS validated version of the cryptographic module if they so require. Fedora based distributions such as RHEL would greatly benefit from this feature in terms of easier long term maintenance.
Benefit to Fedora
It will make Fedora a convenient Linux distribution to use when trying to be FIPS compliant.
Scope
This will not affect developers as it is a packaging change only and no changes to the NSS API are required nor changes to their build systems. The same libraries are shipped as before. They just get distributed among three packages.
The nss shared libraries which are currently distributed as:
nss: libnss3.so, libnssutil3.so, libnssdbm3.so, libssl3.so,
libsmime3.so, libsoftokn3.so, libsoftokn3.chk, libnssckbi.so, libnsspem.so
nss-softokn-freebl: libfreebl3.so, libfreebl3.chk (subpackage of nss)
would be distributed among the packages as:
nss: libnss3.so, libnssdbm3.so, libssl3.so, libsmime3.so, libnssckbi.so, libnsspem.so
nss-softokn: libsoftokn3.so, libsoftokn3.chk
nss-softokn-freebl: libfreebl3.so, libfreebl3.chk (subpackage of softokn) nss-util: libnssutil3.so
Currently nss has a subpackage nss-devel with the headers and development libraries that will get distributed among the new packages. nss-softoken aND nss-util own development subpacakegs will install the portion of the headers of relevamce to them. Each becomes the "owner" of its share of the headers. They will be installed in the same location as before the split so as to make this change transparent to existing client packages.
How To Test
Separately package nss, nss-softokn, and nss-util all having the same version numbers. Separately package nss, and nss-util as the latest release while keeping nss-softokn at an earlier release such as the current release which was FIPS validated. There should not be conflicts at installation time in either of the above cases. Components that depend on NSS should install without conflicts There should be no regressions for components that depend on NSS. Examples of these are glibc, mod_nss, nss_compat_nss, crypto-utils, openswan, xulrunner, evolution, and Pidgin's libpurple.
Building NSS : pre-flight and test
For a description on how to perform and test major nss updates see https://fedoraproject.org/wiki/Updating_NSS#Updating_NSS The above applies to Fedora and RHEL-6 and above.
User Experience
Neither developers nor end users should notice any difference with the exception seeing more packages being installed if they look closely at their yum installs or upgrades.
Dependencies
Upstream NSS 3.12.4 where some code reorganization was made to facilitate this work.
Contingency Plan
There are two contingency plans in case this split cannot be accomplished in time. 1) Make softokn and util sub-packages of nss instead of stand-alone packages. 2) Revert to using the current monolithic approach.
Documentation
- This proposal has been implemented in Rawhide
Release Notes
- The softokn cryptographic module of NSS has been split off as the nss-softokn package
Comments and Discussion