openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#5383) olc* not present in subschema subentry
by hyc＠symas.com 17 Feb '08

17 Feb '08

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: RE24 > OS: OpenSUSE Linux 10.3 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (84.163.120.38) > > > IMO a show-stopper for 2.4.8! > > The schema elements for back-config (olc*) are not present/readable in the > subschema subentry. They are present with the very same config in RE23. Note > that the schema elements have to be retrieved by schema-aware clients for doing > the right thing... In RE24 the config schema are only exposed for DEVEL builds. This is not a regression from 2.4.7 or any other 2.4 releases, so this is certainly not a show-stopper. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5383) olc* not present in subschema subentry
by michael＠stroeder.com 17 Feb '08

17 Feb '08

Full_Name: Michael Ströder Version: RE24 OS: OpenSUSE Linux 10.3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.120.38) IMO a show-stopper for 2.4.8! The schema elements for back-config (olc*) are not present/readable in the subschema subentry. They are present with the very same config in RE23. Note that the schema elements have to be retrieved by schema-aware clients for doing the right thing...

1 0

Re: (ITS#5361) cert verification failures with GnuTLS and DNS subjectAltName
by hyc＠symas.com 16 Feb '08

16 Feb '08

Howard Chu wrote: > A fix has been committed in the GnuTLS code base. For reference, the discussion on gnutls-devel was here http://lists.gnu.org/archive/html/gnutls-devel/2008-02/msg00005.html -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5361) cert verification failures with GnuTLS and DNS subjectAltName
by hyc＠symas.com 16 Feb '08

16 Feb '08

A fix has been committed in the GnuTLS code base. -------- Original Message -------- Subject: Re: (ITS#5361) cert verification failures with GnuTLS and DNS subjectAltName Date: Fri, 15 Feb 2008 23:11:32 +0200 From: Nikos Mavrogiannopoulos <nmav(a)gnutls.org> To: Howard Chu <hyc(a)symas.com> CC: Joe Orton <joe(a)manyfish.co.uk>, gnutls-devel(a)gnu.org References: <200802100917.m1A9HkSb015171(a)boole.openldap.org> <200802152216.25025.nmav(a)gnutls.org> <47B5F843.8080503(a)symas.com> On Friday 15 February 2008, Howard Chu wrote: > > Anyway, does the attached > > patch solve your problem? > > Not really. It still returns a size one byte larger than expected for the > strings. Even in languages where NUL-terminated strings are the norm, the > terminating byte is not included in the length. > > The point is, we expect this API to return exactly the data that was in the > certificate. If the caller wants to treat the data as a string, they can > NUL-terminate it themselves. The manpage only says that the data will be > returned, it does not say that it will be altered in any way. Actually you are right. The return value shouldn't be increased (this also happens in the other similar functions). I've corrected the patch and commited at: http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=commitdiff;h=4cc3c6b6ed0… regards, Nikos -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

RE: (ITS#5336)
by quanah＠zimbra.com 15 Feb '08

15 Feb '08

A similar bug has been reported in the debian bug tracking system, with some debugging information and reproducibility steps. <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465915> --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5381) ldap_result error
by hyc＠symas.com 15 Feb '08

15 Feb '08

fabio.ubaldi(a)coritel.it wrote: > Full_Name: Fabio Ubaldi > Version: 2.3.27 > OS: Linux kernel 2.6.18 > URL: > Submission from: (NULL) (194.237.142.11) > It seems that the error happens only if the two process runs > simultaneously (I use a dual core PC). Thinking of a race condition > error , I used the libldap_r library to build process, but the error > still remains. Processes are completely separate (unless you happen to be using explicitly shared memory). It's pretty much impossible for any code in libldap to be directly responsible for the behavior you're reporting. If you're using a new socket for each request and not closing them when done, it's likely that you're running out of free ports in your system. > The openldap version is 2.3.27 both for slapd servers and the libraries. > > Have anyone encountered a similar error ? > > Thanks in advance for the reply There is no indication of a bug in OpenLDAP Software here. This ITS will be closed. Since it's most likely an issue in how you coded your application, you can followup to the OpenLDAP-software mailing list if you want to discuss this further. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5369) GSSAPI support for client library
by kurt＠OpenLDAP.org 15 Feb '08

15 Feb '08

I note that the patch appears to be incomplete. No gssapi.c included. -- Kurt On Feb 14, 2008, at 8:26 PM, kurt(a)openldap.org wrote: > You've only included one of the two required statements. You need > also need to include either a copyright + license statement, or a > public domain release statement. -- Kurt > > On Feb 14, 2008, at 9:12 AM, mimir(a)samba.org wrote: > >> >> --OgqxwSJOaUobr8KG >> Content-Type: text/plain; charset=iso-8859-2 >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> Kurt, >> >> On Mon, Feb 11, 2008 at 09:06:19AM -0800, Kurt Zeilenga wrote: >>>> Full_Name: Rafal Szczesniak >>>> Version: HEAD >>>> OS: GNU/Linux >>>> URL: http://www.samba.org/~mimir/gssapi-head.diff >>> >>> The submitted patch file does not contain (at the top of the file, >>> not = >> =20 >>> as part of the diffs) the required notices. Please review=20 >>> http://www.openldap.org/devel/contributing.html and insert >>> appropriate=20 >>> notices. Also, please don't include in the diffs derived files >>> (e.g.,=20 >>> configure). >> >> I've updated the patch file with necessary changes. Please take a >> look >> if it's fine now. >> >> >> cheers, >> --=20 >> Rafal Szczesniak >> Samba Team member http://www.samba.org >> Likewise Software http://www.likewisesoftware.com >> >> >> --OgqxwSJOaUobr8KG >> Content-Type: application/pgp-signature; name="signature.asc" >> Content-Description: Digital signature >> Content-Disposition: inline >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.6 (GNU/Linux) >> >> iD8DBQFHtJLCHvdfyv3qiKkRArL0AJ9ZazJE3LUduZb3A8rz21KheW/EYQCfQt8z >> F7AnIDF5EkJ7ssDwHStryEo= >> =tIVf >> -----END PGP SIGNATURE----- >> >> --OgqxwSJOaUobr8KG-- >> >> > >

1 0

(ITS#5382) JLDAP
by jim＠willeke.com 15 Feb '08

15 Feb '08

Full_Name: Jim Willeke Version: N/A OS: Several URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (67.76.26.2) This code: String o1="cn=admin, ou=marketing, o=corporation"; String o2="ou=marketing, o=corporation"; DN dn1 = new DN(o1.toString()); DN dn2 = new DN(o2.toString()); if(dn1.isDescendantOf(dn2)) { System.out.println(dn1 + " isDescendantOf "+ dn2); } if(dn2.isDescendantOf(dn1)) { System.out.println(dn2 + " isDescendantOf "+ dn1); } o1="ou=marketing, o=corporation"; o2="cn=admin, ou=marketing, o=corporation"; dn1 = new DN(o1.toString()); dn2 = new DN(o2.toString()); if(dn1.isDescendantOf(dn2)) { System.out.println(dn1 + " isDescendantOf "+ dn2); } if(dn2.isDescendantOf(dn1)) { System.out.println(dn2 + " isDescendantOf "+ dn1); } Yields these results: ou=marketing,o=corporation isDescendantOf cn=admin,ou=marketing,o=corporation ou=marketing,o=corporation isDescendantOf cn=admin,ou=marketing,o=corporation Sure looks wrong to me.

1 0

Re: (ITS#5380) master slapd hangs when writing
by quanah＠zimbra.com 15 Feb '08

15 Feb '08

--On Friday, February 15, 2008 10:34 AM +0000 ali.pouya(a)free.fr wrote: > Full_Name: Ali Pouya > Version: 2.3.36 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (145.242.11.4) > > > My directory is formed with 4 servers syncronized through syncrepl > (RefreshAndPersist). > THe directory contains about 10 million entries in the BDB back-end. > My slapd servers are configured with the default 16 threads. > I have a JAVA injector for write operations. The injector establishes 28 > connections to the master and writes about 1400 entries per minute. > > After several hours of activity the master hangs. It accepts TCP > connections but does not handle LDAP operations. LDAP requests remain > hanged until interruption by the client. The replicas are OK. strace is useless. Please get a backtrace of all the threads using gdb. Make sure you compiled with debugging symbols, and that slapd is not stripped. I'd also advise getting a backtrace on a current release, as there have been a number of race conditions and cleanup fixes made since 2.3.36. You may want to wait on 2.3.41 which will be released in the next few days. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5381) ldap_result error
by fabio.ubaldi＠coritel.it 15 Feb '08

15 Feb '08

Full_Name: Fabio Ubaldi Version: 2.3.27 OS: Linux kernel 2.6.18 URL: Submission from: (NULL) (194.237.142.11) Hi all, I have two processes running on the same PC that receive data from an LDAP server. Each process opens a connection with a different "slapd" server (i.e each server runs on a different PC) and launches "search" requests at a fixed rate (about 100 searches/s). Each process creates a thread that polls the server responses using the API "ldap_result" the used macro are LDAP_RES_ANY and LDAP_MSG_ONE. When the two processes send the requestes one of the two "ldap_result" return with error (-1) and the error is "Can't contact the LDAP server". I tried to launch one processes and it works fine (the maximum measured rate is 800 searches/s). Also I launch the two processes alternating the search requestes and it works fine. It seems that the error happens only if the two process runs simultaneously (I use a dual core PC). Thinking of a race condition error , I used the libldap_r library to build process, but the error still remains. The openldap version is 2.3.27 both for slapd servers and the libraries. Have anyone encountered a similar error ? Thanks in advance for the reply

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs