Bug 83938

Summary: openldap-2.0.27-2.7.3 breaks ldap_getfirstfilter()
Product: [Retired] Red Hat Linux Reporter: Kenn Humborg <kenn>
Component: openldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED WONTFIX QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: srevivo
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-02 11:34:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kenn Humborg 2003-02-10 11:48:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

Description of problem:

After upgrading to the openldap-2.0.27-2.7.3, 
my web500gw web-to-ldap gateway broke.

Some investigation suggests that the call
to ldap_getfirstfilter() fails here:

    /* try all filters til we have success */
    for (fi = ldap_getfirstfilter(r->r_access->a_filtd, filtertype, search_filter);
        fi != NULL; fi = ldap_getnextfilter(r->r_access->a_filtd)) {

A printf("got here") shows that we get to the line before,
but we never get either into the body of the for-loop, nor
do we get to the code after the end of the loop.

The main web500gw process catches a child signal at this point, 
and HTML output stops.

I'll try and find time to play with this a bit more, but
right now I've had to rollback to openldap-2.0.23-4, with
all its attendent security problems :-(

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Don't have a simple test case yet.

Additional info:

Comment 1 Kenn Humborg 2003-02-27 18:07:46 UTC
ldap_getfirstfilter() and friends are obsoleted anyway
(and are removed completely in OpenLDAP 2.1.x).  So
there's no point in worrying about this anymore.

I've fixed my immediate problem by statically linking
web500gw against OpenLDAP 2.0.23.

You can resolve this as WONTFIX or whatever is most appropriate.