[Dovecot] dovecot-auth core dumps

[Cassidy B. Larson]

Sorry about the no 'bt full'.

Program received signal SIGSEGV, Segmentation fault.
0x00000000107712a8 in gss_delete_sec_context () from /usr/lib/libgssapi.so.8
(gdb) bt full
#0  0x00000000107712a8 in gss_delete_sec_context () from
/usr/lib/libgssapi.so.8
No symbol table info available.
#1  0x00000000004140cb in mech_deinit ()
No symbol table info available.
#2  0x000000000040f38f in auth_request_handler_flush_failures ()
No symbol table info available.
#3  0x0000000000421df9 in io_loop_handle_timeouts ()
No symbol table info available.
#4  0x000000000042287a in io_loop_handler_run ()
No symbol table info available.
#5  0x0000000000421eca in io_loop_run ()
No symbol table info available.
#6  0x0000000000411dfb in main ()
No symbol table info available.

I use the 'masteruser' config on my proxies to let me accept secure
passwords before I proxy off the connection to the storage servers. I
suppose I could disable gssapi on the proxies, but figured I'd send this
your way just in case there was a looming issue.  I believe gssapi did work
in the past, but can't quite remember.

-c


On 8/1/07, Timo Sirainen <tss at iki.fi> wrote:
>
> On Wed, 2007-08-01 at 13:01 -0600, Cassidy B. Larson wrote:
> > It appears the issue is when someone uses gssapi to authenticate.
> > Hope this is what you want:
> ..
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00000000107712a8 in gss_delete_sec_context ()
> > from /usr/lib/libgssapi.so.8
>
> I would have still wanted "bt full", but .. So you really have allowed
> GSSAPI authentication for your proxy? Does it work normally? If not, how
> about just disabling it? :) I've no idea if it's supposed to even work..
>
>
>