Segfault in LDAPerror() when errnum is out of bounds

[Sean Burford]

Hi,

2009/3/20 Michael Ströder <michael at stroeder.com>

> many thanks for digging through this. Does that mean your issues with
> syncrepl controls and l_ldap_result3() are fixed?


Yeah.  There are still mysteries, but RefreshOnly works well enough for now.

I'm wondering why controls are stripped from search results (it would be
nice to get the control that says whether a syncrepl result is an add/modify
or delete for example).  Is this just a side effect of optimisation of the
usual code path?

Any particular reason why you're using python-ldap 2.3.1 which is almost
> two years old?


It came with my distro.


> Sean Burford wrote:
> > When LDAPError receives an errnum from ldap_get_option(l,
> > LDAP_OPT_ERROR_NUMBER, &errnum) that is out of bounds it causes a
> > segfault.  I have attached a script that triggers it and patch that
> > fixes it.
>
> So after applying your patch I get this generic LDAPError exception
> below. This is definitely more robust.


Glad to help.

-- 
Thanks,
Sean Burford
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ldap/attachments/20090320/4db9dc3f/attachment.html>