list mechs bug in cyrus-sasl 2.1.22 and memory leak
Quanah Gibson-Mount
quanah at zimbra.com
Thu Jan 24 03:09:15 EST 2008
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,DIGEST-MD
5,DIGEST-MD5,DIGEST-MD5,GSSAPI,GSSAPI,GSSAPI,LOGIN,LOGIN,LOGIN,OTP,OTP,OTP,PLAIN,PLAIN,PLAIN]
Client mechlist:
[PLAIN,PLAIN,PLAIN,OTP,OTP,OTP,LOGIN,LOGIN,LOGIN,GSSAPI,GSSAPI,GSSAPI,DIGEST
-MD5,DIGEST-MD5,DIGEST-MD5,CRAM-MD5,CRAM-MD5,CRAM-MD5,ANONYMOUS,ANONYMOUS,ANONYMOUS,EXTERNAL]
We have the following mechs:
[PLAIN,PLAIN,PLAIN,LOGIN,LOGIN,LOGIN,GSSAPI,GSSAPI,GSSAPI,DIGEST-MD5,DIGEST-
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
More information about the Cyrus-sasl
mailing list