🐛 Summary
If LDAP Signing is enforced the tool can't bind as it uses only LDAP over 389.
To reproduce
Steps to reproduce the behavior:
Enable LDAP Signing as per Microsoft documentation: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/enable-ldap-signing-in-windows-server
Try and run the application.
Expected behavior
SnafflePy by @robert-todora
Beginning the snaffle...
[!!!] Unable to bind to ldap://10.10.1.100:389 - cleartext
[!!!] Connection is not established