-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TCP Connection not closed if non SSL ldaptor LDAPServer accessed via SSL #170
Comments
OzzieIsaacs
changed the title
TCP Connection not closed if non SSL ldaptor LDAPServer accecced via SSL
TCP Connection not closed if non SSL ldaptor LDAPServer accessed via SSL
Apr 12, 2020
I believe I am facing the same issue while working with an AD server with SSL. Everything works fine but keep seeing this error in the logs right after the proxy sends 'LDAPUnbindRequest':
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using ldaptor for testing the ldap login routines of my code. The ldaptor LDAPServer acts as server in this usecase. One of the testcases is accessing a non SSL server (ldaptor) via SSL configured client (my code).
The server reacts with a log output:
and the TCP connection doesn't get closed, which causes the client to never return. (This looks similar to #137).
I tried to debug the code a little bit, it hits the following line in pureber.py:
print(str(UnknownBERTag(i, context))) # TODO
If I add an line afterwards
raise UnknownBERTag(i, context)
the code closes the connection via the general exception handler with a traceback in twisted (not the best solution, but better than now).
Steps to reproduce (tested with Linux Mint 19.3 python 3.6, using ldaptor 19.1.0):
ldapsearch -H ldaps://127.0.0.1:10389 -x
Excecuting the same command (with 'ldaps' address) on an openldap server (also configured nonSSL) it returns immediately with
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
(My hack leads to the same result).Would be great if you could find a proper solution for this.
Thanks a lot
The text was updated successfully, but these errors were encountered: