[asterisk-bugs] [Asterisk 0012163]: Asterisk segfaults when 'md5secret = userPassword' in res_ldap.conf

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12163 
====================================================================== 
Reported By:                gservat
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12163
Category:                   Resources/res_config_ldap
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-06-2008 14:31 CST
Last Modified:              03-07-2008 11:50 CST
====================================================================== 
Summary:                    Asterisk segfaults when 'md5secret = userPassword'
in res_ldap.conf
Description: 
Hi,

I had res_config_ldap working relatively well when I decided to change
md5secret to point at 'userPassword'. Reason for this is that I prefer to
manage one password attribute for each user, and not 2. Now, when I try and
connect from a SIP client, Asterisk segfaults (every time). If I change
md5secret back to AstAccountRealmedPassword, it starts working again
(sometimes it allows me to login with any password, other times it requires
the right password .. but that's another issue altogether)

I've attached the backtrace from gdb. Unfortunately my C is not good
enough (nor  my knowledge of the Asterisk internals) to troubleshoot this
one. I will happily test if someone finds the problem and attaches a
patch.

Thanks in advance!
====================================================================== 

---------------------------------------------------------------------- 
 gservat - 03-07-08 11:50  
---------------------------------------------------------------------- 
Hi, sorry about that. I wasn't aware that document existed. I've just
uploaded backtrace.txt as per the instructions.

I did a bit more investigating and it appears that, even though when I use
ldapsearch I see the userPassword string in plain ASCII, it's encoded in
the DB itself. I was talking to suretec (Gavin) about this and he said
since res_config_ldap.c uses libldap, it should receive the string the way
that ldapsearch receives it (ie. plain text). Anyway, not sure if this
helps, just thought I'd mention the outcome that I got from digging in a
little. I hope the backtrace.txt helps track down the issue.

Thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-07-08 11:50  gservat        Note Added: 0083609                          
======================================================================