Red Hat Bugzilla – Bug 1027618
tls_reqcert try has bad behavior
Last modified: 2016-07-19 16:27:32 EDT
+++ This bug was initially created as a clone of Bug #1027613 +++
Description of problem:
'tls_reqcert try' option has bad behavior on client side. It should allow connection if certificate is not specified.
man page says:
try The server certificate is requested. If no cer‐
tificate is provided, the session proceeds nor‐
mally. If a bad certificate is provided, the ses‐
sion is immediately terminated.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Setup ldap server with certificates
2.remove all TLS_CACERT and TLS_CACERTDIR from /etc/openldap/ldap.conf
3.set TLS_REQCERT try to /etc/openldap/ldap.conf
4. try ldapsearch -ZZ -x -H ldap://<server_name> '*'
ldap_start_tls: Connect error (-11)
additional info: TLS error -8172:Peer's certificate issuer has been marked as not trusted by the user.
ldapsearch should pass
--- Additional comment from David Spurek on 2013-11-07 03:37:52 EST ---
if TLS_REQCERT allow is set then ldapsearch pass. TLS_REQCERT try and allow should have the same behavior in case if no ca cert is specified (according to description in man ldap.conf).
I think the description talks about the server certificate, not CA certificate.
With the 'try' option, the server will be requested to send it's certificate. The server will send it and the validation will fail on the client side, because you have no CA configured.
The same will happen with 'allow'.
I believe that the 'try' and 'allow' options have no valid purpose at the moment. The server will always send it's certificate. And I guess that these two options are some relict of old SSL versions, where the server didn't have to authenticate to the client.
You should better check with the OpenLDAP upstream.
I forgot add link to upstream discussion - http://www.openldap.org/lists/openldap-technical/201311/msg00099.html
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.