Bug 1310069 - ldap_install_tls reports TLS was established even after a socket timeout
Summary: ldap_install_tls reports TLS was established even after a socket timeout
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openldap
Version: 7.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Matus Honek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1283798
TreeView+ depends on / blocked
 
Reported: 2016-02-19 11:32 UTC by Jakub Hrozek
Modified: 2018-08-04 16:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1395289 (view as bug list)
Environment:
Last Closed: 2018-08-04 16:48:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
a reproducer (3.88 KB, text/plain)
2016-02-19 11:32 UTC, Jakub Hrozek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jakub Hrozek 2016-02-19 11:32:41 UTC 
Created attachment 1128516 [details]
a reproducer

Description of problem:
When there is an LDAP server listening on ldaps:// but the connection attempt is not successfull and interrupted with LDAP_OPT_X_TLS_CONNECT_CB, ldap_install_tls still returns LOCAL_ERROR which indicates the connection was established.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
please see the attached C reproducer.

Actual results:


Expected results:


Additional info:
this happens with both NSS and OpenSSL as crypto back ends.
Note You need to log in before you can comment on or make changes to this bug.