openldap-bugs

openldap-bugs@openldap.org

1 participants
20961 discussions

Re: (ITS#6056) Samba4 breaks OpenLDAP over ldapi
by hyc＠symas.com 26 May '09

26 May '09

abartlet(a)samba.org wrote: > Full_Name: Andrew Bartlett > Version: CVS HEAD > OS: Fedora 10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (59.167.251.137) > > > Samba4's provision and 'make test' seems to create some internal situation in > OpenLDAP slapd where it will not accept any more connections over ldapi:/// > > This is best seen by building Samba4, and running > > TEST_LDAP=yes OPENLDAP_ROOT=/usr/local make test > > The slapd does not crash, but simply stops accepting new connections. Samba4 > currently then crashes due to some other bug (the LDAP backend not responding is > clearly untested code in Samba4). > > It isn't a Samba4 client bug, as ldapsearch also fails to respond. > > This seems very, very similar to ITS#5261 Further testing with Andrew's kvm image shows the hang only occurs when Cyrus SASL's libsasldb2.so plugin is present. I always remove that plugin from my installs, since I only use in-directory SASL secrets. That's probably why I wasn't seeing the reported behavior before. Also a note - it's still not clear we've been talking about the same thing up to this point. Even when the samba test suite hangs, I see that ldapsearch still works fine against slapd. At any rate, currently all of the samba4 tests pass for me. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

LDAP add *.ldif errors
by Pastore Annamaria 25 May '09

25 May '09

Goodmornig, I load a version 2.4 of LDAP (that support overlay-memberof). Ldap it start ok, and the network was ok. I start to configure a memberof scenarios and after few errors started. For don't touch anymore, I cleanup all /var/lib/ldap...and I try to load A single *.ldif.... but when I try to load a .ldif (core, cosine..) I have few errors : 1. With ldap online : ldapadd -x -D "cn=Manager,dc=pippo,dc=it" -W -f core.ldif Enter LDAP Password: adding new entry "cn=core,cn=schema,cn=config" ldap_add: Insufficient access (50) In /var/lib/ldap there is a DB_CONFIG (before DB_CONFIG.exemple) and the owner of directory is ldap, just I read few threads about this sort of bug. The access in slapd.con is : #access to dn="" by * read access to attrs=userPassword by anonymous auth by self write by * auth # by * none access to * by self write by * read # by * none But anymore I try also whit "by * write" and nothing change. Other parameter is : directory /var/lib/ldap 2. With ldap offline : [root@itmit2vl5 schema]# slapadd -l core.ldif -f ../slapd.conf bdb(dc=telecom,dc=it): Program version 4.4 doesn't match environment version 4.6 bdb_db_open: Database cannot be opened, err -30971. Restore from backup! bdb(dc=pippo,dc=it): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem bdb(dc=pippo,dc=it): txn_checkpoint interface requires an environment configured for the transaction subsystem bdb_db_close: txn_checkpoint failed: Invalid argument (22) backend_startup_one: bi_db_open failed! (-30971) slap_startup failed But the bdb version not appears anywhere!!! I try also the command "od -j12 -N8 -tx4 log.0000000001" and the result was 4.6! What I must to do, for going on ? Thank you very much at all, and sorry for my newbie expierence..... Internet E. Mail Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred.

1 0

Re: (ITS#6139) slapd: password-hash rejects multiple values
by michael＠stroeder.com 25 May '09

25 May '09

fumiyas(a)osstech.co.jp wrote: > My /etc/openldap/slapd.conf has the following line: > password-hash {CRYPT} {SSHA} What exactly do you want to achieve by this? Ciao, Michael.

1 0

Compile error on tru64 5.1b
by Didier Godefroy 25 May '09

25 May '09

Hello, Compiling openldap 2.4.26 on tru64 unix v5.1b, using the native compilers and gmake. I'm getting an error as follows: Entering subdirectory liblunicode gmake[2]: Entering directory `/usr/local/openldap/openldap-2.4.16/libraries/liblunicode' cc -O4 -g3 -w -I../../include -I../../include -pthread -I/usr/local/include -pthread -I/usr/local/include -c -o ure.o ure.c cc: Fatal: A memory access violation (bus error or segmentation fault) has occurred. Please submit a problem report. gmake[2]: *** [ure.o] Error 1 I retried, just in case, and got the same error again. I'm not a C programmer and I have no idea how to fix this. What can I try and send to get this fixed? Thanks, -- Didier Godefroy mailto:dg@ulysium.net Support anti-Spam legislation. Join the fight http://www.cauce.org/

2 1

Re: (ITS#6131) "TLSVerifyClient try" not working with GNU TLS
by hyc＠symas.com 25 May '09

25 May '09

subbarao(a)computer.org wrote: > Full_Name: Kartik Subbarao > Version: 2.4.16 > OS: Debian 5.0.1 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (76.99.175.5) > > > When TLSVerifyClient is set to "try", OpenLDAP improperly rejects SSL > connections without a client certificate. The problem appears to start with this > section of code in tls.c around line 1564: > > #ifdef HAVE_GNUTLS > if ( ld->ld_options.ldo_tls_require_cert != LDAP_OPT_X_TLS_NEVER ) { > err = tls_cert_verify( ssl ); > if ( err&& ld->ld_options.ldo_tls_require_cert != LDAP_OPT_X_TLS_ALLOW > ) > return err; > } > #endif > > tls_cert_verify() calls gnutls_certificate_verify_peers2(), which appears to > return error 49 when no client certificate is presented. tls_cert_verify() > doesn't seem to distinguish between this case, and the case of an invalid client > certificate, returning -1 in both cases. > This bug report makes no sense; the code you quoted is not part of OpenLDAP 2.4.16. The relevant code is in function tlsg_session_accept() in tls_g.c, and there is no such bug in that function. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#6140) nadf.schema: AttributeType not found: "lastModifiedTime"
by michael＠stroeder.com 25 May '09

25 May '09

Full_Name: Michael Ströder Version: RE24 OS: Linux URL: Submission from: (NULL) (84.163.124.107) When including nadf.schema slapd does not start and prints error message: /opt/openldap-RE24/etc/openldap/schema/nadf.schema: line 111 objectclass: AttributeType not found: "lastModifiedTime" /etc/openldap/slapd.conf: line 17: <include> handler exited with 1! Analyzing this I found this commented declaration in cosine.schema: ## Deprecated in favor of modifyTimeStamp #attributetype ( 0.9.2342.19200300.100.1.23 NAME 'lastModifiedTime' # DESC 'RFC1274: time of last modify, replaced by modifyTimestamp' # OBSOLETE # SYNTAX 1.3.6.1.4.1.1466.115.121.1.53 # USAGE directoryOperation ) So it seems nadf.schema is not usable at the moment.

1 0

(ITS#6139) slapd: password-hash rejects multiple values
by fumiyas＠osstech.co.jp 25 May '09

25 May '09

Full_Name: SATOH Fumiyasu Version: 2.4.16 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (115.176.213.88) My /etc/openldap/slapd.conf has the following line: password-hash {CRYPT} {SSHA} On OpenLDAP 2.4.16, slapd (slaptest) rejects this config: # /usr/sbin/slaptest /etc/openldap/slapd.conf: line 36: <password-hash> extra cruft after <hash>. slaptest: bad configuration file! On OpenLDAP 2.3.43, slapd (slaptest) accept this config. The slapd.conf(5) (included in OpenLDAP 2.3.43/2.4.16) manpage said: password-hash <hash> [<hash>...] This option configures one or more hashes to be used in generation of user passwords stored in the userPassword attribute during processing of LDAP Password Modify Extended Operations (RFC 3062).

1 0

Re: (ITS#6104) race condition with cancel operation
by h.b.furuseth＠usit.uio.no 23 May '09

23 May '09

hyc(a)symas.com writes: >> Bitflags should be unnecessary as such, just need a set of values. >> Though it wouldn't hurt if they were chosen so one could use bit >> operations to reduce checks for "o_abandon == A or B". "Suppress >> response" value mentioned in ITS#6138 also needed, maybe that must be a >> bitflag when combined with Cancel stuff. > > Yes, it still seems some bitflags will be more appropriate. As long as we decide which flag combinations are (not) valid. Problem with "unrestricted" bitflags compared to a list of values is that they allow and thus require support for flag combinations we have no real need to support. >> Question: >> syncprov_op_abandon() holds&si->si_ops_mutex when setting >> so->s_op->o_abandon. Does it need that? The function needs to >> grab op->o_conn->c_mutex when called as Cancel, but must not do >> that while holding&si->si_ops_mutex since Abandon grabs the >> locks in the opposite order. > > syncprov_op_abandon() can remove ops from the list, so yes, it must > hold si_ops_mutex. Right, but does it need si_ops_mutex while setting o_abandon? Cancel could remove the op, unlock si_ops_mutex, lock c_mutex, update o_abandon. Alternative: Lock c_mutex first (that must be safe since Abandon is doing it anyway), then lock si_ops_mutex. So it's not a critical difference, just that a lock must be held a bit longer. -- Hallvard

1 0

Re: (ITS#6104) race condition with cancel operation
by hyc＠symas.com 23 May '09

23 May '09

h.b.furuseth(a)usit.uio.no wrote: > Well, this turned out a lot of problems. Currently blocked by > ITS#6138 Bad Cancel/Abandon/"internal abandon"/Syncprov interactions. > > back-relay/op.c done (ITS#6133). syncprov/retcode issues may fit better > under ITS#6138. > > Bitflags should be unnecessary as such, just need a set of values. > Though it wouldn't hurt if they were chosen so one could use bit > operations to reduce checks for "o_abandon == A or B". "Suppress > response" value mentioned in ITS#6138 also needed, maybe that must be a > bitflag when combined with Cancel stuff. Yes, it still seems some bitflags will be more appropriate. > Some tidbits uglifying a fix: > * op->o_conn->c_mutex is locked when be->be_abandon() is called, > but not when be->be_cancel() is called. > * send_ldap_ber() needs the lock while it holds&conn->c_write1_mutex, > but code elsewhere indicates the reverse lock order. > > Question: > syncprov_op_abandon() holds&si->si_ops_mutex when setting > so->s_op->o_abandon. Does it need that? The function needs to > grab op->o_conn->c_mutex when called as Cancel, but must not do > that while holding&si->si_ops_mutex since Abandon grabs the > locks in the opposite order. syncprov_op_abandon() can remove ops from the list, so yes, it must hold si_ops_mutex. -- -- Howard Chu CTO, 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#6104) race condition with cancel operation
by h.b.furuseth＠usit.uio.no 23 May '09

23 May '09

Well, this turned out a lot of problems. Currently blocked by ITS#6138 Bad Cancel/Abandon/"internal abandon"/Syncprov interactions. back-relay/op.c done (ITS#6133). syncprov/retcode issues may fit better under ITS#6138. Bitflags should be unnecessary as such, just need a set of values. Though it wouldn't hurt if they were chosen so one could use bit operations to reduce checks for "o_abandon == A or B". "Suppress response" value mentioned in ITS#6138 also needed, maybe that must be a bitflag when combined with Cancel stuff. Some tidbits uglifying a fix: * op->o_conn->c_mutex is locked when be->be_abandon() is called, but not when be->be_cancel() is called. * send_ldap_ber() needs the lock while it holds &conn->c_write1_mutex, but code elsewhere indicates the reverse lock order. Question: syncprov_op_abandon() holds &si->si_ops_mutex when setting so->s_op->o_abandon. Does it need that? The function needs to grab op->o_conn->c_mutex when called as Cancel, but must not do that while holding &si->si_ops_mutex since Abandon grabs the locks in the opposite order. -- Hallvard

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