Bug 591237 - Rebase mod_nss in RHEL 5.6
Summary: Rebase mod_nss in RHEL 5.6
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution (Show other bugs)
(Show other bugs)
Version: 5.6
Hardware: All Linux
low
medium
Target Milestone: rc
: ---
Assignee: RHEL Product and Program Management
QA Contact: Ondrej Hudlicky
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-11 17:47 UTC by Rob Crittenden
Modified: 2010-05-11 17:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-11 17:54:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Rob Crittenden 2010-05-11 17:47:27 UTC
mod_nss unknowningly relied on broken behavior in NSS prior to 3.11.9 related to forking and PKCS#11 modules. The PKCS#11 spec says that after a fork a PKCS#11 module needs to reinitialize. The old NSS soft token didn't require this but most hardware modules do. In mod_nss 1.0.3, the version in RHEL, we initialize mod_nss in the Apache parent process and the children inherit this initialization. We need to initialize NSS in each Apache child instead. This is fixed in mod_nss 1.0.8.

The Certificate System also needs some more advanced OCSP configuration that is available in 1.0.8. While these can be backported through patches the resulting mod_nss 1.0.3 code would be virtually indistinguishable from 1.0.8 and yet we would still have to carry and maintain the patches. It would be better to rebase mod_nss.

Comment 1 Rob Crittenden 2010-05-11 17:54:37 UTC
closing, apparently the rebase bug is enough.


Note You need to log in before you can comment on or make changes to this bug.