Re: list mechs bug in cyrus-sasl 2.1.22 and memory leak

[Ken Murchison <murch@xxxxxxxxxxxxxx>]

I'll see if I can find a Mac on which to test the stock SASL source.  If 
Apple is modifying our source code, then you may have to take this up 
with them.



Quanah Gibson-Mount wrote:
> Me too.  This problem only occurs on the Mac (PPC or i386), and does not 
> show up on linux at all.  I'm guessing this is due to the Mac having a 
> slightly different source tree.  I've verified it goes back as far as 
> 2.1.18.
>
> The multi-listed mechanisms was what pointed me in the direction of 
> SASL, as that was what showed up in the OpenLDAP backtrace.
>
> --Quanah
>
> --On Thursday, January 24, 2008 1:05 PM -0500 Ken Murchison 
> <murch@xxxxxxxxxxxxxx> wrote:
>
> > I don't have access to a Mac to play with, but I can't reproduce this on
> > my Linux dev box.  I'm curious why each of the plugin mechs is listed 3
> > times.
> >
> >
> > Quanah Gibson-Mount wrote:
> > > In playing on the Mac platform, I found there is a bug in the mechanism
> > > listing code on both PPC and x86 Mac.  From testsuite.c:
> > >
> > > Testing sasl_listmech()...
> > > [EXTERNAL,ANONYMOUS,ANONYMOUS,ANONYMOUS,CRAM-MD5,CRAM-MD5,CRAM-MD5,DIGES
> > > T-MD
> > >
> > > 5,DIGEST-MD5,DIGEST-MD5,GSSAPI,GSSAPI,GSSAPI,LOGIN,LOGIN,LOGIN,OTP,OTP,O
> > > TP,PLAIN,PLAIN,PLAIN]
> > >
> > > Client mechlist:
> > > [PLAIN,PLAIN,PLAIN,OTP,OTP,OTP,LOGIN,LOGIN,LOGIN,GSSAPI,GSSAPI,GSSAPI,DI
> > > GEST
> > >
> > > -MD5,DIGEST-MD5,DIGEST-MD5,CRAM-MD5,CRAM-MD5,CRAM-MD5,ANONYMOUS,ANONYMOU
> > > S,ANONYMOUS,EXTERNAL]
> > >
> > > We have the following mechs:
> > > [PLAIN,PLAIN,PLAIN,LOGIN,LOGIN,LOGIN,GSSAPI,GSSAPI,GSSAPI,DIGEST-MD5,DIG
> > > EST-
> > >
> > > MD5,DIGEST-MD5,CRAM-MD5,CRAM-MD5,CRAM-MD5,ANONYMOUS,ANONYMOUS,ANONYMOUS,
> > > EXTERNAL]
> > >
> > >  Currently Still Allocated:
> > >    302EE0 (  360)      00  00  00  00  00  00  00  00  00  00  00  00
> > >    ... 302EA0 (   20)      01  00  00  00  00  00  00  00  D0  '.' '0'
> > >    00  ... 302CC0 (  360)      00  00  00  00  00  00  00  00  00  00
> > >    00  00  ... 302C80 (   20)      01  00  00  00  00  00  00  00  B0
> > >    ',' '0' 00  ... 300AE0 (   20)      00  00  00  00  00  00  00  00
> > >    00  00  00  00  ... 300A40 (   20)      00  00  00  00  00  00  00
> > >    00  00  00  00  00  ... Failed with: memory error
> > >
> > >
> > > Does anyone know of a fix for this?  I can't imagine I'm the first to
> > > hit it.  It's causing problems with OpenLDAP, as after a while the
> > > server will crash, and the stack trace on the core points to this being
> > > the issue.
> > >
> > > Thanks!
> > >
> > > --Quanah
> > >
> > > --
> > >
> > > Quanah Gibson-Mount
> > > Principal Software Engineer
> > > Zimbra, Inc
> > > --------------------
> > > Zimbra ::  the leader in open source messaging and collaboration
> >
> >
> > --
> > Kenneth Murchison
> > Systems Programmer
> > Project Cyrus Developer/Maintainer
> > Carnegie Mellon University
>
>
>
> --
>
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> --------------------
> Zimbra ::  the leader in open source messaging and collaboration


--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University