search for: auth_request_set_login_usernam

Using kmail with PLAIN authentication worked fine with beta3 but trying it with beta4 authentication fails. This is because kmail sends "username \0 username \0 password" in the authorization token and the new code to call auth_request_set_login_username() when supplied an authid must be returning failure (certainly commenting this code out returns to the beta3 behaviour of successfully authenticating). I had a quick look at the routine to see why it might be failing but didn't really work out what its supposed to do. cheers mark

...r dovecot: master: Dovecot v2.2.15 starting up for imap, pop3, lmtp, sieve (core dumps disabled) Sep 29 08:51:05 my_server dovecot: master: Warning: /mnt is no longer mounted. See http://wiki2.dovecot.org/Mountpoints Sep 29 08:51:41 my_server dovecot: auth: Panic: file auth-request.c: line 1252 (auth_request_set_login_username): assertion failed: (*username != '\0') Sep 29 08:51:41 my_server dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a7126a] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a712d6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a70cac] -> dovecot/auth [...

...d34 "file %s: line %d (%s): assertion failed: (%s)", args=0xbff8f154 "\207?\a\bg\003") at failures.c:440 No locals. #5 0x0806c199 in i_panic ( format=0x807bd34 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 No locals. #6 0x08056bd4 in auth_request_set_login_username (request=0x9060148, username=0x8f901b0 "", error_r=0xbff8f1d8) at auth-request.c:871 __PRETTY_FUNCTION__ = "auth_request_set_login_username" #7 0x08056c8f in auth_request_set_username (request=0x9060148, username=0x8f9018a "masteruser", error_r=0xbff8f1d8)...

...panic ( format=format at entry=0x807a0c4 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:276 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0} args = 0xbfd1ca14 "\257j\a\b\371\004" #6 0x0805873a in auth_request_set_login_username (request=0x8a945d8, username=0x8a7c548 "", error_r=0xbfd1cad4) at auth-request.c:1273 master_passdb = <optimized out> __FUNCTION__ = "auth_request_set_login_username" #7 0x08054c44 in master_input_auth_request (conn=conn at entry=0x8aa18b8, args...

...d34 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfe7a5a4 "\207?\a\bg\003") at failures.c:440 No locals. #5 0x0806c199 in i_panic ( format=0x807bd34 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 No locals. #6 0x08056bd4 in auth_request_set_login_username (request=0x87bebc8, username=0x86691b0 "", error_r=0xbfe7a628) at auth-request.c:871 __PRETTY_FUNCTION__ = "auth_request_set_login_username" #7 0x08056c8f in auth_request_set_username (request=0x87bebc8, username=0x866918a "masteruser", error_r=0xbfe7a628)...

...e quota status of an address with the local-part starting with the same character as 'auth_master_user_separator', dovecot/auth crash: > > My 'auth_master_user_separator' is '*' > > Sep 29 08:51:41 my_server dovecot: auth: Panic: file auth-request.c: line 1252 (auth_request_set_login_username): assertion failed: (*username != '\0') v2.2.17 fixes this crash, but a better fix would be to disale the separator for these lookups. I think something like this would work: auth_master_user_separator = * protocol quota-status { # disable auth_master_user_separator = } or alternat...