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

2015-05-13 Thread Dan White
Thomas, I've installed a standard jessie/amd64 installation running the same versions you are and I cannot reproduce. I've tried testsaslauthd, pop3d, and smtptest using both a known good username and a bad username (webmaster), using a for loop to simulate rapid connections. If you can enable c

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

2015-05-12 Thread Thomas Kupka
Dan, the only lead I could have is a correlation between peaks of failed login attempts (from malicious sources most likely, at a rate of precisely one attempt every 5 seconds) and the segfaults. Does this help? extract from mail.log: May 10 10:17:50 mail cyrus/pop3[23539]: badlogin: no-data [60.

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

2015-05-12 Thread Dan White
Thomas, Can you provide a reproducible case? e.g., does this happen on the first authentication attempt after starting saslauthd (with the shadow backend), or are there other factors at play that you can identify? On 05/12/15 11:08 +0200, Thomas Kupka wrote: I have changed the backend to pam an

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

2015-05-12 Thread Thomas Kupka
I have changed the backend to pam and had no segfaults for the last 3 days. Seem like only the shadow backend has this issue. On Fri, May 8, 2015 at 9:10 AM, Thomas Kupka wrote: > > On Wed, 6 May 2015 09:10:15 -0500 Dan White wrote: > > > Can you get a backtrace from the core dump, and debug ou

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

2015-05-08 Thread Thomas Kupka
On Wed, 6 May 2015 09:10:15 -0500 Dan White wrote: > Can you get a backtrace from the core dump, and debug output, e.g.: > > saslauthd -d -c -m /var/spool/postfix/ It does not seem that debug gives out any interesting information. Here are the last lines from when the child processes died: sasl

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

2015-05-06 Thread 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[

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

2015-05-03 Thread Thomas Kupka
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 7faffd5d8c8a sp 000