openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

(ITS#5715) segfault in libdb
by michael＠stroeder.com 29 Sep '08

29 Sep '08

Full_Name: Michael Ströder Version: RE24 OS: openSUSE Linux 11.0 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.103.245) HI! I'm experiencing seg faults when using SASL/EXTERNAL bind when connected over ldapi://. I will try to examine this further. segfault at 0 ip b7f21d4c sp b370fd10 error 6 in libdb-4.6.so[b7ef9000+14f000] Ciao, Michael.

1 0

Re: (ITS#5709) slapd sync provider skips some objects
by sylvain.thomas＠gmail.com 29 Sep '08

29 Sep '08

This is not a patch suggestion but may be it helps to better see the problem's origin : I applied the following patch to syncprov.c and I got good results. The concerned objects are sent with a NULL cookie but they are replicated well. The contextCSN is made up by the subsequent objects. Thanks and best regards Sylvain Thomas. ============================================ --- syncprov.c.orig 2008-09-29 11:08:36.000000000 +0200 +++ syncprov.c 2008-09-29 11:10:33.000000000 +0200 @@ -1642,8 +1642,6 @@ } } else { /* internal ops that aren't meant to be replicated */ - ldap_pvt_thread_rdwr_wunlock( &si->si_csn_rwlock ); - return SLAP_CB_CONTINUE; } /* Don't do any processing for consumer contextCSN updates */

1 0

(ITS#5714) [feature request] operational attrs defined via configuration
by ando＠sys-net.it 27 Sep '08

27 Sep '08

Full_Name: Pierangelo Masarati Version: HEAD OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (151.30.78.88) Currently, the attributeType statement does not allow to define operational attributes. The rationale was that operational attributes are somehow application-maintained, so configuration-defined attrs would be essentially unmaintainable. At the same time, modules that are able to maintain operational attributes can register them bypassing some of the checks attributes defined via configuration must pass. However, the availability of the "relax" control could make this restriction too strict. In fact, there are works in progress (e.g. draft-wahl-ldap-adminaddr) that define operational attrs which could easily be defined via configuration and maintained via the relax control. This is a feature request to suggest the possibility to define operational attrs via configuration. p.

1 0

Re: (ITS#5712) Could not set the connection timeout
by ando＠sys-net.it 27 Sep '08

27 Sep '08

essiambl(a)gmail.com wrote: > Full_Name: Luc-André Essiambre > Version: 2.4.11 > OS: Solaris 10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (216.95.235.3) > > > I'm using openldap to authenticate users for our subversion repositories hosted > on apache httpd. Immediately after a server startup, I get these strange errors > saying "LDAP: Could not set the connection timeout" This message does not come from anything distributed with OpenLDAP software, so it does not help isolate your issue. > when I try to authenticate > myself. The weird thing is, after a couple of attempts at accessing the > subversion content (5 or 6 times), I'm eventually authenticated without error. > Then it will work for a while, then those same errors will come back. You don't specify in what sense you're using OpenLDAP: do you use the client libraries as part of a third-party clien to do a bind to a third-party server, or do you use OpenLDAP as the LDAP server, or both? If you use the client libraries with a third-party client, did you build it with -DLDAP_DEPRECATED=1 ? This is required to expose deprecated API to clients that make use of them. > openldap was compiled using the gcc compiler included in solaris (version 3.4.3) > without slapd, with cyrus-sasl-2.1.21. Solaris runs as a virtual server on sparc > hardware. In any case, I don't see (yet) an OpenLDAP bug, so you should direct further communications to openldap-technical(a)openldap.org, since your problem mainly addresses interoperation with other software. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

ITS#5713
by ando＠sys-net.it 27 Sep '08

27 Sep '08

Probably, the right fix consists in changing that attr's syntax to DirectoryString, and allow all syntaxes, from "--w-------" to passing the value to strtol(value, NULL, 0) etc. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

Re: (ITS#5711) Password Modify Exop don't return ppolicy control in case of error
by ando＠sys-net.it 27 Sep '08

27 Sep '08

Guillaume.Rousse(a)inria.fr wrote: > When Password Modify ExOp fails, due to ppolicy restrictions, it doesn't return > any ppolicy control. Fixed in HEAD, please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

(ITS#5713) Documentation: olcDbMode incorrect at http://www.openldap.org/doc/admin24/slapdconf2.html
by rtdean＠cytherianage.net 26 Sep '08

26 Sep '08

Full_Name: Ryan T. Dean Version: 2.4.11 OS: FreeBSD 7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (64.124.245.244) The documentation present at http://www.openldap.org/doc/admin24/slapdconf2.html provides an incorrect example for the olcDbMode attribute. The documentation reads: >>> 5.2.6.9. olcDbMode: <integer> This directive specifies the file protection mode that newly created database index files should have. Default: olcDbMode: 0600 <<< However, olcDbMode takes an integer, and slapd will reject a value of 0600. It will accept a value of 600, however, this results in octal permissions 1130, which is -not- what you want. Instead, providing olcDbMode with a value of 384 will result in an octal permission of 0600, which is, I believe, what the documentation is attempting to state.

1 0

Re: ITS#5707 [Fwd: Re: 4.7.25 deadlock]
by quanah＠zimbra.com 26 Sep '08

26 Sep '08

Seriously, what kind of crap is that? They've got a serious flaw in their software, but don't intend to publish the patch? sheesh. --Quanah --On September 26, 2008 6:27:45 AM +0000 hyc(a)symas.com wrote: > So I guess we have to warn people about this one ourselves for a while. > > -------- Original Message -------- > Subject: Re: 4.7.25 deadlock > Date: Thu, 25 Sep 2008 23:15:31 -0700 > From: Michael Ubell <@oracle.com> > To: Howard Chu <hyc(a)symas.com> > > Howard, > > Generally we only post critical patches (data corruption, etc) to the > web site. Since this one only effects those using user defined locks > and does no damage, I don't think it will be posted. > > Mike > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > > -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5712) Could not set the connection timeout
by essiambl＠gmail.com 26 Sep '08

26 Sep '08

Full_Name: Luc-André Essiambre Version: 2.4.11 OS: Solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (216.95.235.3) I'm using openldap to authenticate users for our subversion repositories hosted on apache httpd. Immediately after a server startup, I get these strange errors saying "LDAP: Could not set the connection timeout" when I try to authenticate myself. The weird thing is, after a couple of attempts at accessing the subversion content (5 or 6 times), I'm eventually authenticated without error. Then it will work for a while, then those same errors will come back. openldap was compiled using the gcc compiler included in solaris (version 3.4.3) without slapd, with cyrus-sasl-2.1.21. Solaris runs as a virtual server on sparc hardware.

1 0

Re: (ITS#5711) Password Modify Exop don't return ppolicy control in case of error
by ando＠sys-net.it 26 Sep '08

26 Sep '08

ando(a)sys-net.it wrote: > Guillaume.Rousse(a)inria.fr wrote: > >> When Password Modify ExOp fails, due to ppolicy restrictions, it doesn't return >> any ppolicy control. > > Right: the control is created and attached to SlapReply, but the > callback is slap_cb_null(), and the control is removed from SlapReply > and destroyed before ppolicy_modify() returns. This is because extended > ops do not directly send response, but rather delegate it to the > frontend. I don't see an easy solution, other than taking response into > the exop handlers. An alternative approach would be to use a specific callback response other that slap_cb_null() within passwd_extop() that duplicates and brings back any controls set within the internal modify, so that they can be placed in the SlapReply that is bassed back to send_ldap_extended(). Or, sr_ctrls could become "MUSTBEFREED" much like other SlapReply fields... p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

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