<div dir="ltr"><br><div class="gmail_quote"><div dir="ltr"><div><span class="">On Wed, 6 May 2015 09:10:15 -0500 Dan White <<a href="mailto:dwhite@olp.net" target="_blank">dwhite@olp.net</a>> wrote:<br><br>> Can you get a backtrace from the core dump, and debug output, e.g.:<br>> <br>> saslauthd -d -c -m /var/spool/postfix/<br><br></span>It does not seem that debug gives out any interesting information. Here are the last lines from when the child processes died:<br><br>saslauthd[19194] :do_auth : auth success: [user=thomas] [service=imap] [realm=] [mech=shadow]<br>saslauthd[19194] :do_request : response: OK<br>saslauthd[19195] :rel_accept_lock : released accept lock<br>saslauthd[19193] :get_accept_lock : acquired accept lock<br>saslauthd[19193] :rel_accept_lock : released accept lock<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19193] :do_auth : auth failure: [user=noauth] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19193] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=spam] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19193] :rel_accept_lock : released accept lock<br>saslauthd[19193] :do_auth : auth failure: [user=test] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=info] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19193] :get_accept_lock : acquired accept lock<br>saslauthd[19193] :rel_accept_lock : released accept lock<br>saslauthd[19193] :do_auth : auth failure: [user=admin] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=administrator] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19193] :get_accept_lock : acquired accept lock<br>saslauthd[19193] :rel_accept_lock : released accept lock<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=postmaster] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=sales] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=support] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=webmaster] [service=smtp] [realm=] [mech=shadow] [reason=Incorrect password]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=help] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=contact] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=office] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br>saslauthd[19194] :do_auth : auth failure: [user=staff] [service=smtp] [realm=] [mech=shadow] [reason=Invalid username]<br>saslauthd[19194] :get_accept_lock : acquired accept lock<br>saslauthd[19194] :rel_accept_lock : released accept lock<br><br></div>The failed authentication attempts are certainly malicious software trying out default credentials but they seem to be handled normally.<br><div><span class=""><br>> This backend doesn't get used much these days. pam should functionally<br>> replace it. Does it also produce a segfault?<br><br></span>I will try this. I have shadow backend running for about 10 years now and never had this urge to change it.<span class="HOEnZb"><font color="#888888"><br><br>Thomas<br></font></span></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 6, 2015 at 4:10 PM, Dan White <span dir="ltr"><<a href="mailto:dwhite@olp.net" target="_blank">dwhite@olp.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/03/15 10:24 +0200, Thomas Kupka wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Package: sasl2-bin<br>
Version: 2.1.26.dfsg1-13<br>
Severity: important<br>
File: /usr/sbin/saslauthd<br>
<br>
Dear Maintainer,<br>
<br>
since upgrading to Jessie, all saslauthd processes segfault on a multiple daily basis:<br>
<br>
May 3 06:26:12 mail kernel: [22739.740552] saslauthd[763]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in <a href="http://libc-2.19.so" target="_blank">libc-2.19.so</a>[7faffd557000+19f000]<br>
May 3 06:26:12 mail kernel: [22739.928344] saslauthd[739]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in <a href="http://libc-2.19.so" target="_blank">libc-2.19.so</a>[7faffd557000+19f000]<br>
May 3 06:26:12 mail kernel: [22740.127304] saslauthd[760]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in <a href="http://libc-2.19.so" target="_blank">libc-2.19.so</a>[7faffd557000+19f000]<br>
May 3 10:04:24 mail kernel: [35831.420577] saslauthd[761]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in <a href="http://libc-2.19.so" target="_blank">libc-2.19.so</a>[7faffd557000+19f000]<br>
May 3 10:04:24 mail kernel: [35831.607218] saslauthd[762]: segfault at 0 ip 00007faffd5d8c8a sp 00007ffda85ebe48 error 4 in <a href="http://libc-2.19.so" target="_blank">libc-2.19.so</a>[7faffd557000+19f000]<br>
May 3 10:04:24 mail postfix/smtpd[17269]: warning: SASL authentication failure: cannot connect to saslauthd server: Connection refused<br>
</blockquote>
<br>
Can you get a backtrace from the core dump, and debug output, e.g.:<br>
<br>
saslauthd -d -c -m /var/spool/postfix/var/run/saslauthd -a shadow<br>
<br>
I can't reproduce your segfault on my unstable system running<br>
2.1.26.dfsg1-13. However, I'm several version behind on some of the linked<br>
libraries.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-- Configuration Files:<br>
/etc/default/saslauthd changed:<br>
START=yes<br>
DESC="SASL Authentication Daemon"<br>
NAME="saslauthd"<br>
MECHANISMS="shadow"<br>
</blockquote>
<br>
This backend doesn't get used much these days. pam should functionally<br>
replace it. Does it also produce a segfault?<span><font color="#888888"><br>
<br>
-- <br>
Dan White<br>
</font></span></blockquote></div><br></div>
</div></div></div><br></div>