Bug 498542
Summary: | need mod_nss "forking model" code in the RHEL version | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Christina Fu <cfu> |
Component: | mod_nss | Assignee: | Rob Crittenden <rcritten> |
Status: | CLOSED ERRATA | QA Contact: | Chandrasekar Kannan <ckannan> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.5 | CC: | benl, dpal, kchamart, kwright, mharmsen |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-13 22:38:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 443788, 496342 |
Description
Christina Fu
2009-04-30 23:48:52 UTC
build complete Some Notes from rcrit: ------------------------------------------------------------------ mod_nss 1.0.3 initialized NSS and then forked its child listeners. This was allowed by older NSS versions but was not the correct thing to do under the PKCS#11 spec and therefore broke in some hardware readers which enforced the spec. mod_nss 1.0.8 initializes NSS after forking each child. So you basically just need to test that mod_nss still works. If you have access to a hardware device testing that you can use keys/certs stored on that with mod_nss would be a good way to test too. --------------------------------------------------------------- Verified: RHEL5.6(x86_64, i386) Version: mod_nss-1.0.8-2.el5.x86_64.rpm mod_nss does work fine with the new build Successful run of beaker auto tests -- https://beaker.engineering.redhat.com/jobs/27209 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0049.html |