Bug 796808
Summary: | slapd segfaults when certificate key cannot be loaded | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Vcelak <jvcelak> |
Component: | openldap | Assignee: | Jan Vcelak <jvcelak> |
Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | jsynacek, omoris, tsmetana |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openldap-2.4.23-21.el6 | Doc Type: | Bug Fix |
Doc Text: |
- openldap server configured to use TLS, some problem when loading server key appears
- server crashes with segmentation fault due to accessing uninitialized memory
- applied patch to initialize variables holding TLS certificate and key correctly
- server no longer crashes in described situation, but log the information about to failure and continues in execution
|
Story Points: | --- |
Clone Of: | 772890 | Environment: | |
Last Closed: | 2012-06-20 07:29:27 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: | 772890 | ||
Bug Blocks: |
Description
Jan Vcelak
2012-02-23 17:21:32 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: - openldap server configured to use TLS, some problem when loading server key appears - server crashes with segmentation fault due to accessing uninitialized memory - applied patch to initialize variables holding TLS certificate and key correctly - server no longer crashes in described situation, but log the information about to failure and continues in execution 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/RHSA-2012-0899.html |