Hi, have dovecot 2.0.13 running fine on a NetBSD box, with lots of clients happily authenticating to it with GSSAPI. I've just updated an ArchLinux box to latest new version which has meant its switched from using heimdal to using mit krb5 and its kmail is now also slightly newer. Thunderbird successfully authenticates to dovecot from this machine but kmail now fails. Kmail reports: Unable to authenticate via GSSAPI. The server ... replied: SASL(-1): generic failure: GSSAPI Error: Invalid token was supplied (Token header is malformed or corrupt) The dovecot log reports: Feb 27 13:42:18 bats dovecot: auth: GSSAPI(mark at ECS.VUW.AC.NZ,130.195.5.88): Invalid base64 data in continued response Any suggestions on how to track down what specifically has changed and how to fix it? cheers mark
On Mon, 2012-02-27 at 14:17 +1300, Mark Davies wrote:> Feb 27 13:42:18 bats dovecot: auth: > GSSAPI(mark at ECS.VUW.AC.NZ,130.195.5.88): Invalid base64 data in > continued responseLooks like kmail is sending some kind of garbage to Dovecot. Set auth_debug_passwords=yes to make Dovecot log the auth traffic.
On 02/27/12 23:32, Timo Sirainen wrote:> Looks like kmail is sending some kind of garbage to Dovecot. Set > auth_debug_passwords=yes to make Dovecot log the auth traffic.Yeah, I did a network trace and it seems kmail is not sending the full authentication request before trying to carry on.> 8 0.043625 130.195.5.88 130.195.5.13 IMAP 898 Request: 1 AUTHENTICATE GSSAPI YIICWgYJKoZIhvcSAQICAQBuggJJMI[...]jLyNiRZFsc9zFxpdwrZAB/WXRRS1zsM4SlDfE59CW1xfKAkqe > 9 0.044919 130.195.5.13 130.195.5.88 IMAP 70 Response: + > 10 0.045413 130.195.5.88 130.195.5.13 IMAP 80 Request: 2 LIST "" "" > 11 0.045486 130.195.5.13 130.195.5.88 IMAP 122 Response: 1 NO [ALERT] Invalid base64 data in continued responsenow to figure out why its started truncating it. cheers mark