I need to add an important note here: Even this bug is marked as fixed, the change in Cyrus SASL now breaks RFC 4752. See my comment: https://github.com/cyrusimap/cyrus-sasl/issues/419#issuecomment-566981689
Technically, one would now need to create an issue in Launchpad that Cyrus SASL GSSAPI mech is broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in 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 Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Bionic: Triaged Status in cyrus-sasl2 source package in Cosmic: Triaged Bug description: [Status] Awaiting upstream fix. [Workaround] Unknown. [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 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/1015819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
