12 messages in net.sourceforge.lists.courier-usersRe: [courier-users] upgrade issue wit...
FromSent OnAttachments
ivan mitevJan 11, 2007 1:57 pm 
ivan mitevJan 14, 2007 11:44 pm 
Sander HolthausJan 15, 2007 6:11 am 
Sam VarshavchikJan 15, 2007 7:24 am 
Jay LeeJan 15, 2007 7:40 am 
Jay LeeJan 15, 2007 8:13 am 
Sam VarshavchikJan 15, 2007 8:28 am 
Jay LeeJan 15, 2007 9:50 am 
ivan mitevJan 15, 2007 12:01 pm 
ivan mitevJan 15, 2007 12:24 pm 
Sam VarshavchikJan 15, 2007 5:30 pm 
ivan mitevJan 16, 2007 1:35 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] upgrade issue with courier-authlib 0.58 -> 0.59 / ldap authActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jan 15, 2007 5:30:45 pm
List:net.sourceforge.lists.courier-users

ivan mitev writes:

replacing l_simple_bind_s() with ldap_simple_bind_s() like it was in 0.58 seems to fix the problem

since there's no other reference to sasl in authlib's ldap module,  that should be safe ...

ldap_simple_bind_s has been replaced by ldap_sasl_bind_s. That part of the story is true.

The real problem, that you've now pointed me to, is the call to strlen() on a null pointer, in l_simple_bind_s.

This should really fix this, properly:

diff -U3 -r1.58 authldaplib.c --- authldaplib.c 12 Nov 2006 19:54:10 -0000 1.58 +++ authldaplib.c 16 Jan 2007 01:30:14 -0000 @@ -197,7 +197,7 @@ { struct berval cred;

- cred.bv_len=strlen(passwd); + cred.bv_len=passwd ? strlen(passwd):0; cred.bv_val=(char *)passwd;

return ldap_sasl_bind_s(ld, who, NULL, &cred, NULL, NULL, NULL);