Thank you for figuring this out! I guess we need to see how upstream
wants to address the issue before we can address it in Ubuntu? Given the
root cause, it seems to me that it would only be appropriate for Ubuntu
to do what upstream does here to fix it.
** Description changed:
[Status]
- This bug needs a developer to reproduce the problem and locate the root
- cause.
+ Awaiting upstream fix.
[Workaround]
Unknown.
-
- [Missing]
-
- Exact steps to reproduce.
[Description]
Not sure if this is a problem with openldap or cyrus-sasl2 at this
point.
Using sasl binding only works with ldapsearch when not using ssl or tls.
If either ssl or tls is used I see this ouput from -d 1 from ldapsearch:
sb_sasl_generic_pkt_length: received illegal packet length of 813957120 bytes
sasl_generic_read: want=16, got=16
0000: 00 7e 02 01 00 78 84 00 00 00 5d 0a 01 02 04 00 .~...x....].....
sb_sasl_cyrus_decode: failed to decode packet: generic failure
sb_sasl_generic_read: failed to decode packet
ldap_read: want=8 error=Input/output error
# numResponses: 0
ldap_result: Can't contact LDAP server (-1)
tls_write: want=165 error=Connection reset by peer
tls_write: want=165 error=Bad file descriptor
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- sb_sasl_generic_pkt_length: received illegal packet length when using
ldapsearch and sasl with ssl or tls
+ sb_sasl_generic_pkt_length: received illegal packet length when using Active
Directory and ldapsearch and sasl with ssl or tls
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet length when using
Active Directory and ldapsearch and sasl with ssl or tls
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
