Re: SASL: encoded packet size too big

2019-08-16 Thread Eugene via dovecot
of the AP-REP is interpreted as packet length. I will ask cyrus-sasl project for further help. Sorry for the hassles. On 8/15/19 4:14 PM, Eugene via dovecot wrote: > I see nothing suspicious in FreeIPA slapd logs because connection drops > before SASL negotiation completion. > Net

Re: SASL: encoded packet size too big

2019-08-15 Thread Eugene via dovecot
l configuration? >> I can dump connection session and send pcap file here. >> >> On August 15, 2019 7:27:20 AM GMT+03:00, Aki Tuomi >> wrote: >> >> On 15/08/2019 00:34 Eugene via dovecot wrote: >> The next combination of parameters makes 100% LD

Re: SASL: encoded packet size too big

2019-08-14 Thread Eugene via dovecot
The next combination of parameters makes 100% LDAP connections unsuccessful (the log snippet form the previous mail). sasl_bind = yes sasl_mech = gssapi tls = yes Looks like this combination is utterly incorrect and should be prohibited (tls must not be used when mech is gssapi). https://lists.f

SASL: encoded packet size too big

2019-08-14 Thread Eugene via dovecot
Hello! Dovecot uses it's own SASL implementation, doesn't it? Aug 14 23:45:23 example.com auth[10428]: GSSAPI client step 1 Aug 14 23:45:23 example.com auth[10428]: encoded packet size too big (813804546 > 65536) Aug 14 23:45:23 example.com dovecot[10085]: auth-worker(104

Authdb NSS module

2019-07-14 Thread Eugene via dovecot
Hello! Upgrading manual tells that authdb [NSS module was removed][1] some time ago. [1]: https://wiki2.dovecot.org/Upgrading/2.3#line-100 > userdb nss was removed. Use userdb passwd instead. Can this change be reverted? I'd like to use only libnss_sss.so.2 as dovecot userdb source. It's also