[Pkg-openldap-devel] [fijal@irys.um.pabianice.pl: slapd crash]

[Torsten Landschoff]

----- Forwarded message from Jan Fijalkowski <fijal at irys.um.pabianice.pl> -----

X-Original-To: torsten at localhost
X-Flags: 0000
Date: Sun, 30 Apr 2006 13:55:53 +0200
From: Jan Fijalkowski <fijal at irys.um.pabianice.pl>
To: torsten at debian.org
Subject: slapd crash
X-Enigmail-Version: 0.94.0.0
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: -2 (not scanned, spam filter disabled)
X-GMX-UID: 65xnfHs9MmAptORwYmFnODkxMjQ1N123
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on stargate.galaxy
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.3

Hello!

I'm using Yours debian openldap packages for sarge (slapd, ldap-utils
etc. 2.2.23-8).
I've found that using certain extended filters causes  slapd crash.
Example:

$ ldapsearch -x ':dn:2.5.13.5:=People'
goes OK, but
$ ldapsearch -x ':dn:2.5.13.7:=People'
causes server crash

The same effect You can obtain using this filter from gq, so I think
that this is a server problem.
This bug look very grave, because every user can crash the server (even
remotely). That's the reason I'm writing directly to You. On the other
side, I suppose that the problem lies in openldap source.
The same effect remains with version 2.2.26-5 ported to sarge.

All the best!

fijal

P.S.
Thank You for the good job with openldap packages - with normal use they
work perfectly - almost all vital services in my job depends on them :-)


----- End forwarded message -----