Description of problem:
I'm trying to upgrade my RHEL3 ldap directory to RHEL4 to use with Outlook 2003.
Outlook returns with "unavailable critical extension".
Following links discuss the problem.
When I try to stop advertisement of pagedResults using
access to dn.exact="" attrs=supportedControl val=1.2.840.1135188.8.131.529
by * none
I get Segmentation Fault.
Version-Release number of selected component (if applicable):
# slapd -V
@(#) $OpenLDAP: slapd 2.2.13 (Mar 22 2007 17:53:35) $
Steps to Reproduce:
1.Add access line above to slapd.conf
2.run slaptest or service ldap start
Same as when I remove access statement.
I've attempted to contacted openldap.org for help but they suggested I get
support from RedHat instead.
See attached file for slapd.conf
Created attachment 157346 [details]
Test LDAP server config
This is config causes slaptest to fail unless I remove the access line.
Created attachment 157357 [details]
patch resolving the issue
I found a patch upstream, which fixed the issue on my test box - it does not
crash anymore. However, I do not have MS Outlook here, so I am not able to
test, if the ACL rule applies. Could you please test it? You can find .srpm at
Thanks in advance.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
(In reply to comment #2)
> Created an attachment (id=157357) 
> patch resolving the issue
> I found a patch upstream, which fixed the issue on my test box - it does not
> crash anymore. However, I do not have MS Outlook here, so I am not able to
> test, if the ACL rule applies. Could you please test it? You can find .srpm at
> Thanks in advance.
The patch did the trick. It does not crash anymore and Outlook queries the
server just fine.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.