Bug 1010224
| Summary: | NSS 3.15 breaks SSL in OpenLDAP clients | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alicja Kario <hkario> | ||||
| Component: | nss | Assignee: | Elio Maldonado Batiz <emaldona> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Alicja Kario <hkario> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.5 | CC: | azelinka, borgan, eparis, kengert, omoris, rrelyea, sforsber, tlavigne | ||||
| Target Milestone: | beta | Keywords: | Regression | ||||
| Target Release: | 6.5 | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | nss-softokn-3.14.3-8.el6 nss-3.15.1-9.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: The nss-softoken self test did not check whether freebl was properly initialized before running its tests.
Consequence: Client code, such as the LPAD client, may have initialized and finalized nss. In such case freebl would have been claned up and unloaded and when loaded again it would try to run its test and such test would fail resulting in client failures such as TLS connection errors.
Fix: The nss-softoken self test now reinitailizes appropriate parts of freebl before running the RSA checks.
Result: The self tests pass and LDAP queries via TLS succeed.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-11-21 06:20:40 UTC | Type: | Bug | ||||
| 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: | 993793 | ||||||
| Attachments: |
|
||||||
|
Description
Alicja Kario
2013-09-20 10:03:56 UTC
were their any AVC messages which went along with this denial? I've just verified this is not the prelink/freebl issue. This may really be a rebase issue. Using strace, the very last action executed is an attempt to read /usr/lib64/libsoftokn3.chk Immediately after accessing that file, the ldapsearch utility returns the error. I downgraded packages one after the other. With these packages we fail: nss-softokn-3.14.3-6.el6.x86_64 nss-softokn-freebl-3.14.3-6.el6.x86_64 With these packages it works: nss-softokn-3.14.3-3.el6.x86_64 nss-softokn-freebl-3.14.3-3.el6.x86_64 OK, I've solved the initial problem, I now get additional info: TLS error -8172:Peer's certificate issuer has been marked as not trusted by the user. At this point we may be operating where kai has pointed out (that is the trust setup is wrong somewhere). I'm going to attach a patch to fix the failure to initialize NSS. It would be good to see if Hubert's failure is actually a regression. Certainly /etc/openldap/cacerts is not an NSS database directory, so if LDAPTLS_CACERTDIR is supposed to point to an NSS database directory, the failure I'm getting is expected. (The silent "I can't starttls" isn't. Elio is building a new package the removes the fips-selftest code only only leaves the moving the the .chk files into new packages. We'll roll that out in for betat. That is not the patch I'll attach here. I'm looking beyond beta, so this patch won't actually be in the next compose. Created attachment 800803 [details]
Fix the self test to reinitailize appropriate parts of freebl before running the RSA checks.
The problem is ldap is Initializing NSS then Finalizing it. This is perfectly permissible, but the new 'run tests at load time' in softoken are now failing. What happens is normally freebl gets loaded and it's 'at load time' handler gets called, which initializes everything and runs its selftests. Then softoken gets loaded and runs its selftests. Then at Finalize softoken cleans up the freebl state and then unloads. When it loads again, it tries to run it's selftests, but because it freebl was shutdown, the tests will fail. The patch is to try to initialize freebl before running the tests.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1558.html |