Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/281 We are doing TLS configuration incorrectly in the 389 project. The proper way to do it is to use ldap_set_option(ld,...) to set the TLS options such as certdir, cert, key, etc. first, then use ldap_set_option(ld, LDAP_OPT_X_TLS_NEWCTX, &val) last, to tell openldap to create and init a new TLS context with the given configuration.
Please add steps to verify/reproduce this issue
(In reply to comment #3) > Please add steps to verify/reproduce this issue Just verify no regressions in any acceptance, long duration, etc. test that uses TLS/SSL.
I dn't see any particular regressions. Hence marking as VERIFIED.
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: This is not a bug a customer could run into. This was fixed upstream and we wanted to track it.
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-0813.html