openldap-bugs March 2007

openldap-bugs@openldap.org

42 participants
123 discussions

(ITS#4883) test000 fails
by dieter＠dkluenter.de 20 Mar '07

20 Mar '07

Full_Name: Dieter Kluenter Version: HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.187.212.14) I checked out todays cvs and failed with test000, slapd.1.log shows @(#) $OpenLDAP: slapd 2.X (Mar 20 2007 11:57:18) $ dieter@magenta:/work/ldap-src/servers/slapd ldap_pvt_gethostbyname_a: host=magenta, r=0 daemon_init: ldap://localhost:9011/ daemon_init: listen on ldap://localhost:9011/ daemon_init: 1 listeners to open... ldap_url_parse_ext(ldap://localhost:9011/) daemon: listener initialized ldap://localhost:9011/ daemon_init: 2 listeners opened ldap_create lt-slapd init: initiated server. slap_sasl_init: initialized! bdb_back_initialize: initialize BDB backend bdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 10, 2006) hdb_back_initialize: initialize HDB backend hdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 10, 2006) => str2entry: "dn: vendorName: The OpenLDAP Project <http://www.openldap.org/> " >>> dnPrettyNormal: <> <<< dnPrettyNormal: <>, <> <= str2entry() -> 0x822002c bdb_db_init: Initializing BDB database >>> dnPrettyNormal: <o=OpenLDAP Project,l=Internet> => ldap_bv2dn(o=OpenLDAP Project,l=Internet,0) <= ldap_bv2dn(o=OpenLDAP Project,l=Internet)=0 => ldap_dn2bv(272) <= ldap_dn2bv(o=OpenLDAP Project,l=Internet)=0 => ldap_dn2bv(272) <= ldap_dn2bv(o=openldap project,l=internet)=0 <<< dnPrettyNormal: <o=OpenLDAP Project,l=Internet>, <o=openldap project,l=internet> >>> dnPrettyNormal: <cn=Monitor> => ldap_bv2dn(cn=Monitor,0) <= ldap_bv2dn(cn=Monitor)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=Monitor)=0 > ldap_dn2bv(272) <= ldap_dn2bv(cn=monitor)=0 <<< dnPrettyNormal: <cn=Monitor>, <cn=monitor> >>> dnNormalize: <cn=Subschema> => ldap_bv2dn(cn=Subschema,0) <= ldap_bv2dn(cn=Subschema)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=subschema)=0 <<< dnNormalize: <cn=subschema> matching_rule_use_init [...] t-slapd startup: initiated. backend_startup_one: starting "cn=config" config_back_db_open config_build_entry: "cn=config" config_build_entry: "cn=schema" config_build_entry: "cn={0}core" config_build_entry: "cn={1}cosine" config_build_entry: "cn={2}corba" config_build_entry: "cn={3}java" config_build_entry: "cn={4}inetorgperson" config_build_entry: "cn={5}misc" config_build_entry: "cn={6}nis" config_build_entry: "cn={7}openldap" config_build_entry: "cn={8}duaconf" config_build_entry: "cn={9}dyngroup" config_build_entry: "cn={10}ppolicy" config_build_entry: "olcDatabase={-1}frontend" config_build_entry: "olcDatabase={0}config" config_build_entry: "olcDatabase={1}bdb" config_build_entry: "olcDatabase={2}monitor" backend_startup_one: starting "o=OpenLDAP Project,l=Internet" bdb_db_open: o=OpenLDAP Project,l=Internet bdb_db_open: Warning - No DB_CONFIG file found in directory /work/ldap-src/tests/testrun/db.1.a: (2) Expect poor performance for suffix o=OpenLDAP Project,l=Internet. bdb_db_open: dbenv_open(/work/ldap-src/tests/testrun/db.1.a) ====> bdb_cache_release_all backend_startup_one: bi_db_open failed! (1) lt-slapd shutdown: initiated ====> bdb_cache_release_all bdb_db_close: alock_close failed lt-slapd destroy: freeing system resources. slapd stopped. connections_destroy: nothing to destroy. my configure parameters export CFLAGS="-DLDAP_DEVEL" ./configure \ --prefix=/opt/openldap \ --enable-dynamic \ --enable-aci \ --enable-modules \ --enable-rewrite \ --enable-bdb=yes \ --enable-hdb=yes \ --enable-java=mod \ --enable-ldap=mod \ --enable-monitor=yes \ --enable-meta=mod \ --enable-perl=mod \ --enable-relay=mod \ --enable-sql=mod \ --enable-overlays=mod -Dieter

1 0

Re: (ITS#4882) Add doesnt work <OpenStruct message="unknown result (64)", code=64>
by ando＠sys-net.it 20 Mar '07

20 Mar '07

sxm20(a)yahoo.com wrote: > Full_Name: Shailesh Mangal > Version: 2.2.29 > OS: Windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (69.228.83.104) > > > While trying to add entry from Ruby's netLdap library. > > [result = @ldap_con.add(:dn => dn, :attributes => attr)] > > I get following error message. > <OpenStruct message="unknown result (64)", code=64> > > I have also tried it on Linux (debian), getting the same error message The ITS is not for help on software usage; please direct software usage questions to openldap-software. In any case, 2.2.29 is ancient, so even in the case of a bug there are no chances it gets fixed unless it is still present in currently released code. In your case, the error is likely to be on the user's side; see the FAQ for directions about typical user errors; see RFC4511 (or ldap.h) for mapping between result codes and diagnostics. This ITS will be closed. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

(ITS#4882) Add doesnt work <OpenStruct message="unknown result (64)", code=64>
by sxm20＠yahoo.com 19 Mar '07

19 Mar '07

Full_Name: Shailesh Mangal Version: 2.2.29 OS: Windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (69.228.83.104) While trying to add entry from Ruby's netLdap library. [result = @ldap_con.add(:dn => dn, :attributes => attr)] I get following error message. <OpenStruct message="unknown result (64)", code=64> I have also tried it on Linux (debian), getting the same error message

1 0

(ITS#4881) ldapsearch, SSL and segmentation fault
by andrej.groups＠gmail.com 19 Mar '07

19 Mar '07

Full_Name: Andrej Ricnik Version: ldapsearch 2.3.21 OS: Slackware 11 URL: Submission from: (NULL) (138.235.105.2) I'm trying to use ldapsearch against Novell eDir 8.7.3.9 (on Solaris) which works fine when used w/o encryption. If I use the self-signed Cert created on the eDir server ldapsearch segfaults. This works fine (returns the expected 46 DNs): ldapsearch -D cn=wpsbind,ou=wcm,ou=systemusers,ou=users,o=myorg -W -h dev4.kdc.myorg.org -x -s sub -LLL '(cn=*)' This one segfaults after the 45th DN: ldapsearch -ZZ -D cn=wpsbind,ou=wcm,ou=systemusers,ou=users,o=myorg -W -h dev4.kdc.myorg.org -x -s sub -LLL '(cn=*)' It looks similar to ITN# 889 ...

1 0

Re: (ITS#4868) Binary Attribute Patch(es)
by ando＠sys-net.it 19 Mar '07

19 Mar '07

vargok(a)yahoo.com wrote: > Additionally, just FYI, it appears that the regular/standard OpenLDAP > (at least as of 2.3.32) BDB-based backend returns > "userCertificate;binary" just fine (and, actually, all the time, even > when requesting "userCertificate"). I would've expected them to > behave the same way. Right. Time permitting, I'll check why back-sql behaves differently and, in case, how to fix it. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4868) Binary Attribute Patch(es)
by vargok＠yahoo.com 19 Mar '07

19 Mar '07

Additionally, just FYI, it appears that the regular/standard OpenLDAP (at least as of 2.3.32) BDB-based backend returns "userCertificate;binary" just fine (and, actually, all the time, even when requesting "userCertificate"). I would've expected them to behave the same way. ----- Original Message ---- From: Pierangelo Masarati <ando(a)sys-net.it> To: Kevin Vargo <vargok(a)yahoo.com> Cc: openldap-its(a)openldap.org Sent: Wednesday, March 14, 2007 5:05:52 PM Subject: Re: (ITS#4868) Binary Attribute Patch(es) Kevin Vargo wrote: > However, there remains a problem: other LDAP Servers appear to return > the 'attribute-name' requested (userCertificate;binary::) to describe > the data. Now that the data is being returned, it's being returned > without the ";binary" option -- as 'userCertificate::'. Per > ITS#3113, ";binary" is obsoleted? To be honest, I'm not sure I have ever clearly understood that ";binary" issue, and I don't have time to dig out the documentation, learn about it, and check the code, since the whole stuff seems to be obsolete. > Is there a compatibility mode that can be optioned to support this? None that I know of. > Obsoleted and back-wards compatibility being in conflict..... I think compatibility with obsolete stuff is something that may easily get in conflict with open source, volunteer developed software. Volunteers tend to concentrate scarce resources on important things, and preserving compatibility with obsolete (often broken) stuff is first of all a waste of scarce resources, and second, but not least, reduces pressure on obsolete (broken) software makers, which typically are not volunteers but actually get paid for (obsolete/broken stuff). Having said this, you may find volunteers that, pushed by their own needs like to spend time supporting obsolete/broken stuff for the simple reason they need it. > i.e. > is there a way to say "return the attribute by name-requested instead > of schema-name?" No. This question has been raised many times, and the answer has always been like that. All you could do is hack slap_send_search_entry() in servers/slapd/result.c. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------ ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html

1 0

(ITS#4880) HAVE_POSIX_TERMIOS -> HAVE_TERMIOS_H
by ed＠fxq.nl 18 Mar '07

18 Mar '07

Full_Name: Ed Schouten Version: 2.3.x and 2.4.x OS: FreeBSD URL: Submission from: (NULL) (83.180.2.78) The FreeBSD folks are planning on removing the old <sgtty.h> interface from their operating system. On FreeBSD, OpenLDAP still uses this header file, though there is some nice termios code in the source. It isn't used on FreeBSD at the moment, because the code doesn't use the same naming as the definition made by autoconf. A simple %s/HAVE_POSIX_TERMIOS/HAVE_TERMIOS_H/ on the sourcetree fixes this.

1 0

(ITS#4879) URL parse/unparse troubles
by h.b.furuseth＠usit.uio.no 17 Mar '07

17 Mar '07

Full_Name: Hallvard B Furuseth Version: HEAD OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard Here are some URLs parsing/building bugs in libldap/url.c. Some may be design bugs. Possibly some fixes will need backwards bug-compatibility. I show URLs converted from string to LDAPURLDesc format with ldap_url_parse(), back to string format with ldap_url_desc2str() when the result differs from the original, back to LDAPURLDesc... ================ The url.c Novell kludge does not work (for the example URL). If the bug is old and nobody has complained, maybe it should be removed. If it's fixed instead, note that the code looks like it'll handle Novell URLs with '/' in components after hostport: ldap_url_parse_ext() does strchr( url, '/' ) very early to find the end of the hostport. ldap://111.222.333.444:389??cn=abc,o=company -> error 5 (LDAP_URL_ERR_BADURL) Example URL without port number: ldap://111.222.333.444??cn=abc,o=company -> host "111.222.333.444??cn=abc,o=company", DN NULL -> ldap://111.222.333.444??cn=abc,o=company:389/??base ================ ldap_url_desc2str() outputs IPv6 host addresses as "addr" rather than "[addr]". (LDAPURLDesc does not contain the '[]'s in .lud_host, nor any flag which says it's an IPv6 host address). I don't know the syntax of such addresses, but I seem to remember they contains ':'s. If so the parser could fail if an IPv6 address does not contains ':', and the URL builder could test for ':' to determine if there should be [] around the host part. Also, what does stuff between the ']' and ':port' mean? Should anything be allowed there? ldap://[::1]what's this:222/ -> host "::1", port 222 -> ldap://::1:222/??base -> error 5 (LDAP_URL_ERR_BADURL) ================ Converting "%00" to char* should return an error, since the char* will not match the source URL: ldapi://a%00b/cn=d%00e -> host "a", DN "cn=d" -> ldapi://a/cn=d??base ================ The RFCs 4516/2255 hostport part has grammar [host [":" port]], but ldap_url_desc2str() produces [host][":" port]. ldap:// -> host NULL, port 389 -> ldap://:389/??base That's OK as an ldap_url_parse() OpenLDAP extension, but not as ldap_url_desc2str() output given to non-OpenLDAP applications. ================ While I'm writing, I wonder if OpenLDAP 2.4 could omit defaults and final "?"s from the ldap_url_desc2str() output. E.g. ldap:// would become ldap:// and not ldap://:389/??base. But maybe we get into trouble if ldap.conf has another port or something. ================ ldapi URL (un)parsing has several problems: ldap_url_parse() always treats ':' as a host:port separator. Thus one can produce an ldapi LDAPURLDesc with a meaningless port. However ldap_url_desc2str() does not URL-escape ':', and it also takes port!=0 to mean it is not an ldapi URL and needs no '/'-escaping. Similarly filenames with initial '[' do not work. ldapi://%2Ftmp%2Ffoo%3A222/ -> host "/tmp/foo:222" (correct) -> ldapi://%2Ftmp%2Ffoo:222/??base -> host "/tmp/foo", port 222 -> ldapi:///tmp/foo:222/??base -> host NULL, DN "tmp/foo:222/" ldapi://%2Ftmp%2Ffoo:000/ -> host "/tmp/foo" -> ldapi://%2Ftmp%2Ffoo/??base ldapi://%2Ftmp%2Ffoo:bar/ -> error 5 (LDAP_URL_ERR_BADURL) ==== The current implementation would handle some non-Unix ldapi filenames wrong. (They'll need well-defined URL-escaping rules if they get implemented, so it might as well be fixed now.) Of course these can also be strange Unix relative filenames... Windows-like filenames: ldapi://C%3A%2Fldapi/ -> host "C:/ldapi" -> ldapi://C:%2Fldapi/??base -> error 5 (LDAP_URL_ERR_BADURL) Tops-20-like filenames resemble IPv6 addresses (not that I expect to port OpenLDAP to Tops-20:-) ldapi://[ldap.var.run]ldapi/ -> host "ldap.var.run" -> ldapi://ldap.var.run/??base URL-escaping the '[' and ']' does not help; the '[' is lost: ldapi://%5Bldap.var.run%5Dldapi/ -> host "ldap.var.run]ldapi" -> ldapi://ldap.var.run%5Dldapi/??base

1 0

Re: (ITS#4872) Non-portable comparison in wait4msg() (result.c) causes infinite loop
by ando＠sys-net.it 17 Mar '07

17 Mar '07

There might be more about this; in daemon.c, difftime() is used to compute the difference between two time_t, but the result is assigned to a time_t. Maybe a negative value cannot be obtained, but in any case that cast would likely be incorrect as well in systems where time_t is unsigned. I'm re-opening this bug. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: (ITS#4878) removal of duplicate variables in slapd
by ando＠sys-net.it 17 Mar '07

17 Mar '07

bret.lambert(a)gmail.com wrote: > Unnecessary duplicate variables using the same name have been removed with this > patch. > > Found via lint(1) on OpenBSD. Fixed. Thanks, p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs March 2007