Skip to content
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

Error importing TLS_CHANNEL_BINDING from ldap3 #91

Open
3ldidi94 opened this issue Jul 12, 2024 · 2 comments
Open

Error importing TLS_CHANNEL_BINDING from ldap3 #91

3ldidi94 opened this issue Jul 12, 2024 · 2 comments

Comments

@3ldidi94
Copy link

3ldidi94 commented Jul 12, 2024

Hello,

Using the last binary I get the following error message regarding the TLS_CHANNEL_BINDING module in the ldap3 lib.

Traceback (most recent call last):
  File "/tmp/onefile_847008_1720789016_268097/__main__.py", line 27, in <module>
  File "/tmp/onefile_847008_1720789016_268097/ldeep/views/ldap_activedirectory.py", line 10, in <module ldeep.views.ldap_activedirectory>
ImportError: cannot import name 'TLS_CHANNEL_BINDING' from 'ldap3' (/tmp/onefile_847008_1720789016_268097/ldap3/__init__.py)

I tried to install the last available version 2.9.1 of the python3-ldap3 lib from debian stable repo and there is no module called TLS_CHANNEL_BINDING but I don't have this error when installing with python -m pip install git+https://github.com/franc-pentest/ldeep

@tiyeuse
Copy link
Collaborator

tiyeuse commented Jul 17, 2024

It's because ldap3 python library latest release is 2.9.1, which was released on Jul 17, 2021. Many improvements on that library have been added on the github repository and no additional release have been made.
If you do pip install git+https://github.com/franc-pentest/ldeep, it will pull a specific version of the ldap3 library with the new features, including the channel binding one.
I suggest you to keep installing ldeep using the github repo: python -m pip install git+https://github.com/franc-pentest/ldeep.

@BastienFaure
Copy link
Contributor

I will check if we can have a workaround. It shouldn't be an issue to include that in the final binary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants