Displaying 2 results from an estimated 2 matches for "auth_worker_handle_passl".
2007 Aug 01
3
dovecot: child 1690 (auth-worker) killed with signal 11
...sr/local/libexec/dovecot/dovecot-auth /usr/local/stow/dovecot-data/var/run/dovecot/core
GNU gdb 6.3
[...]
Core was generated by `dovecot-auth -w'.
Program terminated with signal 11, Segmentation fault.
[...]
(gdb) bt full
#0 0x00000000 in ?? ()
No symbol table info available.
#1 0x08056954 in auth_worker_handle_passl (client=0x8089e18, id=3,
args=0x808a082 "user=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:242
auth_request = (struct auth_request *) 0x808a3f0
credentials_str = 0x2 <Address 0x2 out of bounds>
#2 0x08056c15 i...
2020 Jan 25
0
Lookup master userdb used with GSSAPI causes auth-worker to report "Error: BUG: PASSL had invalid passdb ID"
...d (I've tried lua and sql) for master passdb
instead of static in combination with GSSAPI client causes auth-worker to
report "Error: BUG: PASSL had invalid passdb ID". I took a look at the code
and my best guess is that in case of GSSAPI + sql/lua master passdb we end
up with call to auth_worker_handle_passl with id that
auth_worker_handle_passl considers invalid. Continuing with guesswork, I
imagine that since GSSAPI doesn't really need passdb in config "virtual"
passdb is generated "on the fly" in code. I even tried explicitly defining
static passdb with mechanisms set to gssa...