Bug#784112: /usr/sbin/saslauthd: saslauthd segfaults

[Dan White]

On 05/03/15 10:24 +0200, Thomas Kupka wrote:
>Package: sasl2-bin
>Version: 2.1.26.dfsg1-13
>Severity: important
>File: /usr/sbin/saslauthd
>
>Dear Maintainer,
>
>since upgrading to Jessie, all saslauthd processes segfault on a multiple daily basis:
>
>May  3 06:26:12 mail kernel: [22739.740552] saslauthd[763]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in libc-2.19.so[7faffd557000+19f000]
>May  3 06:26:12 mail kernel: [22739.928344] saslauthd[739]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in libc-2.19.so[7faffd557000+19f000]
>May  3 06:26:12 mail kernel: [22740.127304] saslauthd[760]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in libc-2.19.so[7faffd557000+19f000]
>May  3 10:04:24 mail kernel: [35831.420577] saslauthd[761]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in libc-2.19.so[7faffd557000+19f000]
>May  3 10:04:24 mail kernel: [35831.607218] saslauthd[762]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in libc-2.19.so[7faffd557000+19f000]
>May  3 10:04:24 mail postfix/smtpd[17269]: warning: SASL authentication failure: cannot connect to saslauthd server: Connection refused

Can you get a backtrace from the core dump, and debug output, e.g.:

saslauthd -d -c -m /var/spool/postfix/var/run/saslauthd -a shadow

I can't reproduce your segfault on my unstable system running
2.1.26.dfsg1-13. However, I'm several version behind on some of the linked
libraries.

>-- Configuration Files:
>/etc/default/saslauthd changed:
>START=yes
>DESC="SASL Authentication Daemon"
>NAME="saslauthd"
>MECHANISMS="shadow"

This backend doesn't get used much these days. pam should functionally
replace it. Does it also produce a segfault?

-- 
Dan White