openldap-bugs

openldap-bugs@openldap.org

1 participants
20965 discussions

Re: (ITS#6194) Patch - Enhancement - provide LDIF support as libldif
by richm＠stanfordalumni.org 12 Apr '10

12 Apr '10

masarati(a)aero.polimi.it wrote: >>>> Sorry about that. You can find it here: >>>> http://rmeggins.fedorapeople.org/ldifutil.c >>>> >>> Gotit, thanks. I have one first comment: the public API does not >>> generally expose the memory context. I'm renaming >>> ldap_parse_ldif_record() as ldap_parse_ldif_record_x(), and eliminating >>> the void *ctx arg from ldap_parse_ldif_record(), if you don't mind. >>> >> tested and applied to HEAD; please test. Thanks, p. >> > > More comments: > > 1) perhaps it may be worth providing a function that converts a LDIFRecord > structure into a string, and one that sends it to a stream > For debugging purposes, or something like that? > 2) I note you put > > LDAPMod **lr_mods; /* list of mods for LDAP_REQ_MODIFY, > LDAP_REQ_ADD */ > struct berval lr_newrdn; /* LDAP_REQ_MODDN, LDAP_REQ_MODRDN, > LDAP_REQ_RENAME */ > struct berval lr_newsuperior; /* LDAP_REQ_MODDN, LDAP_REQ_MODRDN, > LDAP_REQ_RENAME */ > int lr_deleteoldrdn; /* LDAP_REQ_MODDN, LDAP_REQ_MODRDN, > LDAP_REQ_RENAME */ > /* the following are for future support */ > struct berval lr_extop_oid; /* LDAP_REQ_EXTENDED */ > struct berval lr_extop_data; /* LDAP_REQ_EXTENDED */ > struct berval lr_cmp_attr; /* LDAP_REQ_COMPARE */ > struct berval lr_cmp_bvalue; /* LDAP_REQ_COMPARE */ > > in the structure; the last four are not used right now. I think it would > make sense to group struct members by op in substructures, and then put > them in a union, to stress the fact that they're mutually exclusive. Much > like Howard did for the corresponding substructures in the Operation > struct in slapd. > Please check out this patch - ftp://ftp.openldap.org/incoming/openldap-2.4.21-ldifrecord-union-20100412.p… > p. > > > > >

1 0

Re: (ITS#6517) undefined references to ldif_*
by hyc＠symas.com 12 Apr '10

12 Apr '10

Michael Ströder wrote: > hyc(a)symas.com wrote: >> richm(a)stanfordalumni.org wrote: >>> This is most likely related to my recent LDIF changes. But I didn't see >>> this problem. What platform is this? What build flags are you using? >> >> Built fine here too, looks like an inconsistent build tree over there. > > The build with the same build flags on the very same system worked right > before the recent libldif check-ins. I'm using anon CVS pserver for cvs up. The anon CVS server has some lag in receiving updates from the master server. Don't you have an account on the master? -- -- 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#6517) undefined references to ldif_*
by michael＠stroeder.com 12 Apr '10

12 Apr '10

hyc(a)symas.com wrote: > richm(a)stanfordalumni.org wrote: >> michael(a)stroeder.com wrote: >>> Full_Name: >>> Version: HEAD >>> OS: Linux >>> URL: >>> Submission from: (NULL) (84.163.96.140) >>> >>> >>> cc -g -O2 -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -o >>> .libs/ldapurl ldapurl.o lduversion.o -L/dummy/lib >>> ../../libraries/liblutil/liblutil.a ../../libraries/libldap/.libs/libldap.so >>> /usr/src/michael/openldap/HEAD/openldap/libraries/liblber/.libs/liblber.so >>> ../../libraries/liblber/.libs/liblber.so -lsasl2 -lssl -lcrypto -lcrypt -lresolv >>> -Wl,--rpath -Wl,/opt/openldap-HEAD/lib >>> ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_getline' >>> ../../libraries/libldap/.libs/libldap.so: undefined reference to >>> `ldif_countlines' >>> ../../libraries/libldap/.libs/libldap.so: undefined reference to >>> `ldif_parse_line2' >>> ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_debug' >>> collect2: ld returned 1 exit status >>> make[2]: *** [ldapurl] Error 1 >>> make[2]: Leaving directory >>> `/usr/src/michael/openldap/HEAD/openldap/clients/tools' >>> make[1]: *** [all-common] Error 1 >>> make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/clients' >>> make: *** [all-common] Error 1 >>> >>> >> This is most likely related to my recent LDIF changes. But I didn't see >> this problem. What platform is this? What build flags are you using? > > Built fine here too, looks like an inconsistent build tree over there. The build with the same build flags on the very same system worked right before the recent libldif check-ins. I'm using anon CVS pserver for cvs up. Ciao, Michael.

1 0

Re: (ITS#6517) undefined references to ldif_*
by hyc＠symas.com 12 Apr '10

12 Apr '10

richm(a)stanfordalumni.org wrote: > michael(a)stroeder.com wrote: >> Full_Name: >> Version: HEAD >> OS: Linux >> URL: >> Submission from: (NULL) (84.163.96.140) >> >> >> cc -g -O2 -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -o >> .libs/ldapurl ldapurl.o lduversion.o -L/dummy/lib >> ../../libraries/liblutil/liblutil.a ../../libraries/libldap/.libs/libldap.so >> /usr/src/michael/openldap/HEAD/openldap/libraries/liblber/.libs/liblber.so >> ../../libraries/liblber/.libs/liblber.so -lsasl2 -lssl -lcrypto -lcrypt -lresolv >> -Wl,--rpath -Wl,/opt/openldap-HEAD/lib >> ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_getline' >> ../../libraries/libldap/.libs/libldap.so: undefined reference to >> `ldif_countlines' >> ../../libraries/libldap/.libs/libldap.so: undefined reference to >> `ldif_parse_line2' >> ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_debug' >> collect2: ld returned 1 exit status >> make[2]: *** [ldapurl] Error 1 >> make[2]: Leaving directory >> `/usr/src/michael/openldap/HEAD/openldap/clients/tools' >> make[1]: *** [all-common] Error 1 >> make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/clients' >> make: *** [all-common] Error 1 >> >> > This is most likely related to my recent LDIF changes. But I didn't see > this problem. What platform is this? What build flags are you using? Built fine here too, looks like an inconsistent build tree over there. -- -- 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#6517) undefined references to ldif_*
by richm＠stanfordalumni.org 12 Apr '10

12 Apr '10

michael(a)stroeder.com wrote: > Full_Name: > Version: HEAD > OS: Linux > URL: > Submission from: (NULL) (84.163.96.140) > > > cc -g -O2 -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -o > .libs/ldapurl ldapurl.o lduversion.o -L/dummy/lib > ../../libraries/liblutil/liblutil.a ../../libraries/libldap/.libs/libldap.so > /usr/src/michael/openldap/HEAD/openldap/libraries/liblber/.libs/liblber.so > ../../libraries/liblber/.libs/liblber.so -lsasl2 -lssl -lcrypto -lcrypt -lresolv > -Wl,--rpath -Wl,/opt/openldap-HEAD/lib > ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_getline' > ../../libraries/libldap/.libs/libldap.so: undefined reference to > `ldif_countlines' > ../../libraries/libldap/.libs/libldap.so: undefined reference to > `ldif_parse_line2' > ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_debug' > collect2: ld returned 1 exit status > make[2]: *** [ldapurl] Error 1 > make[2]: Leaving directory > `/usr/src/michael/openldap/HEAD/openldap/clients/tools' > make[1]: *** [all-common] Error 1 > make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/clients' > make: *** [all-common] Error 1 > > This is most likely related to my recent LDIF changes. But I didn't see this problem. What platform is this? What build flags are you using?

1 0

(ITS#6517) undefined references to ldif_*
by michael＠stroeder.com 12 Apr '10

12 Apr '10

Full_Name: Version: HEAD OS: Linux URL: Submission from: (NULL) (84.163.96.140) cc -g -O2 -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -Wl,-R/dummy/lib -o .libs/ldapurl ldapurl.o lduversion.o -L/dummy/lib ../../libraries/liblutil/liblutil.a ../../libraries/libldap/.libs/libldap.so /usr/src/michael/openldap/HEAD/openldap/libraries/liblber/.libs/liblber.so ../../libraries/liblber/.libs/liblber.so -lsasl2 -lssl -lcrypto -lcrypt -lresolv -Wl,--rpath -Wl,/opt/openldap-HEAD/lib ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_getline' ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_countlines' ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_parse_line2' ../../libraries/libldap/.libs/libldap.so: undefined reference to `ldif_debug' collect2: ld returned 1 exit status make[2]: *** [ldapurl] Error 1 make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/clients/tools' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/clients' make: *** [all-common] Error 1

1 0

Re: (ITS#6515) A lot of dead links on main page of OpenLDAP man.
by hyc＠symas.com 12 Apr '10

12 Apr '10

mitroko(a)gmail.com wrote: > Full_Name: Dmitry Stremkouski > Version: > OS: GNU/Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (95.84.189.132) > > > Hello guys. The part of OpenLDAP Manual (wich can be found here - > http://www.openldap.org/doc/admin23/schema.html) contains a lot of broken > links. > Please correct. The 2.3 release is no longer maintained. This doc will not be updated. > FE: http://www.alvestrand.no/harald/objectid/ - dead > A: http://www.bsa-global.com/ - dead (doesn't look good enough for global OID > authority) > A: http://www.iana.org/cgi-bin/enterprise.pl - should be (redirect, but futher, > IMHO, will be dead, try http://pen.iana.org/pen/PenApplication.page) > > Thanks. -- -- 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#6516) Proxy backends normalize ordered attrs incorrectly
by masarati＠aero.polimi.it 12 Apr '10

12 Apr '10

> They need to use ordered_value_*() functions instead. Fixed in HEAD. p.

1 0

(ITS#6516) Proxy backends normalize ordered attrs incorrectly
by masarati＠aero.polimi.it 12 Apr '10

12 Apr '10

Full_Name: Pierangelo Masarati Version: HEAD/re24 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (129.72.165.199) Submitted by: ando They need to use ordered_value_*() functions instead. A patch is coming. p.

1 0

Re: (ITS#6513) dynacl/aci fails on searches with attributes
by masarati＠aero.polimi.it 12 Apr '10

12 Apr '10

>> Full_Name: Peter Marschall >> Version: 2.4.21 >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/Peter-Marschall-100411.patch >> Submission from: (NULL) (94.217.135.20) >> >> >> Hi, >> >> Playing around with dynacl/aci a bit I cam across the following issue: >> >> Searches that do not contain the attribute OpenLDAPaci in the list of >> attribues >> queried, omit objects. > > dynacl/aci (as the original aci code it's based on) relies on the fact > that the entry is complete. This is the case when the entry is stored > locally, e.g. in back-bdb/hdb. Otherwise, no mechanism is in place to > retrieve operational attributes. Please note that in the latter case, > even ACL rules based on, say, createTimestamp or so would operate > incorrectly. > > My guess is that you're trying to use ACIs with a non-local storage. In > that case your analysis is correct. Can you provide your (sanitized) > configuration? > > The "right" solution is much more general, not only related to dynacl. > Slapd needs to know in advance what (operational) attributes are required > for policy enforcing, and they need to be added to requested attrs when > entries are collected from remote storage. Your patch seems to fix your > specific need, but it is clearly inefficient. Automatically detecting what attributes need to be added to requests for proxying sounds like an overkill. Probably, a reasonable workaround could be to add a configuration directive that lists what attributes need to be added to requests. This directive should be honored by proxy backends and in general by all those backends that do not pass back complete entries to the frontend. In the case of proxy backends its use would be straightforward, since requested attrs need to be mapped anyway in the request. Adding some more would not be a big deal. Things might be a bit more complicated in case of, say, special configurations like proxycache, where ACIs would need to be added to all attribute templates, and so. Yet another reason to avoid ACIs :) p.

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