openldap-bugs

openldap-bugs@openldap.org

1 participants
21003 discussions

Re: (ITS#5369) GSSAPI support for client library
by hyc＠symas.com 09 Oct '08

09 Oct '08

kurt(a)OpenLDAP.org wrote: > I note that the patch appears to be incomplete. No gssapi.c included. Sorry for the tardy review. The patch is also corrupted (both patches actually) and doesn't compile. Note this section of the patch to cyrus.c: +static ber_int_t +sb_sasl_cyrus_encode( + struct sb_sasl_generic_data *p, + unsigned char *buf, + ber_len_t len, + Sockbuf_Buf *dst) +{ + sasl_conn_t *sasl_context = (sasl_conn_t *)p->ops_private; + ber_int_t ret; + unsigned tmpsize = dst->buf_size; + + ret = sasl_encode( sasl_context, buf, len, + (SASL_CONST char **)&dst->buf_base, + &tmpsize ); - assert( sbiod != NULL ); + dst->buf_size = tmpsize; + dst->buf_end = dst->buf_ The last line appears to be truncated in both versions of the diff. > > -- 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 >>> -- -- 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

SIZELIMIT 0 gives a zero limit
by Fabio Pedretti 08 Oct '08

08 Oct '08

The ldap.conf man page says this: SIZELIMIT <integer> Specifies a size limit to use when performing searches. The number should be a non-negative integer. SIZELIMIT of zero (0) specifies unlimited search size. However it appears that putting "SIZELIMIT 0" in my ldap.conf gives a: # search result search: 2 result: 4 Size limit exceeded To workaround this I put a very large value and it works. I am using openldap 2.4.11 compiled from source on a Slackware 10.0. Is it an openldap bug? Thanks, Fabio

3 3

(ITS#5730) Seg fault with referral entry and search filter (name=some name)
by michael＠stroeder.com 08 Oct '08

08 Oct '08

Full_Name: Michael Ströder Version: RE24 OS: openSUSE Linux 11.0 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.79.146) HI! if searching with (name=some name) slapd seg faults when processing a referral entry (referral chasing is off). If I delete the entry it works. FWIW: It's back-hdb. Ciao, Michael. ------------------- referral entry ------------------- dn: cn=Refers to ldap.openldap.org,ou=Testing,dc=stroeder,dc=de cn: Refers to ldap.openldap.org createTimestamp: 20050228152803Z creatorsName:: Y249TWljaGFlbCBTdHLDtmRlcixvdT1GcmllbmRzLGRjPXN0cm9lZGVyLGRjP WRl entryCSN: 20071213003755.763469Z#000000#000#000000 entryDN: cn=Refers to ldap.openldap.org,ou=Testing,dc=stroeder,dc=de entryUUID: 150b8f52-1de9-1029-9a2d-eaab50cd2b83 hasSubordinates: FALSE modifiersName:: Y249bWljaGFlbCBzdHLDtmRlcixvdT1mcmllbmRzLGRjPXN0cm9lZGVyLGRj PWRl modifyTimestamp: 20051021165032Z objectClass: extensibleObject objectClass: referral ref: ldap://ldap.openldap.org/dc=openldap,dc=org structuralObjectClass: referral subschemaSubentry: cn=Subschema ------------------- excerpt of syslog ------------------- Oct 8 15:44:05 nb2 slapd[10257]: conn=0 op=5 SRCH base="dc=stroeder,dc=de" scope=2 deref=0 filter="(|(name=*some name*))" Oct 8 15:44:05 nb2 slapd[10257]: conn=0 op=5 SRCH attr=telephonenumber countImmSubordinates labeledurl displayName cn subordinateCount objectClass description countTotSubordinates hasSubordinates msDS-Approx-Immed-Subordinates mobile structuralObjectClass subschemaSubentry mail numSubordinates numAllSubordinates homephone uid Oct 8 15:44:05 nb2 slapd[10257]: <= bdb_substring_candidates: (name) not indexed Oct 8 15:44:10 nb2 kernel: slapd[10260]: segfault at 29 ip 08091834 sp b37da2a0 error 4 in slapd[8048000+1e5000] ------------------- end of console debug output ------------------- ldap_url_parse_ext(ldap://ldap.openldap.org/dc=openldap,dc=org) >>> dnPretty: <dc=openldap,dc=org> => ldap_bv2dn(dc=openldap,dc=org,0) <= ldap_bv2dn(dc=openldap,dc=org)=0 => ldap_dn2bv(272) <= ldap_dn2bv(dc=openldap,dc=org)=0 <<< dnPretty: <dc=openldap,dc=org> => send_search_reference: dn="(null)" => access_allowed: read access to "(null)" "entry" requested => dn: [5] dc=stroeder,dc=de Segmentation fault

1 0

Re: (ITS#5729) back-hdb segfaults
by quanah＠zimbra.com 07 Oct '08

07 Oct '08

--On Tuesday, October 07, 2008 7:22 PM +0000 quanah(a)zimbra.com wrote: > Full_Name: Quanah Gibson-Mount > Version: RE24 10/7/2008 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.29.239) > > > I have a database using back-hdb, which segfaults while creating a domain > in the database (zimbra style). Works correctly with dn2id.c 1.158 -> 1.159 patch applied. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5729) back-hdb segfaults
by quanah＠zimbra.com 07 Oct '08

07 Oct '08

Full_Name: Quanah Gibson-Mount Version: RE24 10/7/2008 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.29.239) I have a database using back-hdb, which segfaults while creating a domain in the database (zimbra style). It's clearly logged here: Tue Oct 7 12:16:26 2008 *** Running as zimbra user: /opt/zimbra/bin/zmprov -l cd freelancer.lab.zimbra.com ERROR: service.FAILURE (system failure: unable to create domain: freelancer.lab.zimbra.com) (cause: javax.naming.ServiceUnavailableException freelancer.lab.zimbra.com:389; socket closed) where the socket got closed during the operation (cd means create domain, and would add a dc=freelancer,dc=lab,dc=zimbra,dc=com object in the database). backtrace has: (gdb) bt #0 0x00002b41adac6839 in hdb_dn2id_add (op=0x1d11bc00, txn=0x1dc6ea20, eip=0x1b765080, e=0x1d01f828) at dn2id.c:617 #1 0x00002b41adab2029 in hdb_add (op=0x1d11bc00, rs=0x434aac70) at add.c:329 #2 0x000000000043cecd in fe_op_add (op=0x1d11bc00, rs=0x434aac70) at add.c:334 #3 0x000000000043c857 in do_add (op=0x1d11bc00, rs=0x434aac70) at add.c:194 #4 0x0000000000433d59 in connection_operation (ctx=0x434aadc0, arg_v=0x1d11bc00) at connection.c:1084 #5 0x0000000000434274 in connection_read_thread (ctx=0x434aadc0, argv=0xc) at connection.c:1210 #6 0x00002b41aa6c3a27 in ldap_int_thread_pool_wrapper (xpool=0x1b75fe00) at tpool.c:663 #7 0x00000038dcc061b5 in start_thread () from /lib64/libpthread.so.0 #8 0x00000038dc0cd36d in clone () from /lib64/libc.so.6 #9 0x0000000000000000 in ?? () (gdb) print *eip $2 = {bei_parent = 0x0, bei_id = 0, bei_lockpad = 0, bei_state = 128, bei_finders = 0, bei_nrdn = {bv_len = 0, bv_val = 0x0}, bei_rdn = {bv_len = 0, bv_val = 0x0}, bei_modrdns = 0, bei_ckids = 1, bei_dkids = 0, bei_e = 0x1d01f008, bei_kids = 0x1da3c080, bei_kids_mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\0' <repeats 39 times>, __align = 0}, bei_lrunext = 0x0, bei_lruprev = 0x0} (gdb) print *eip->bei_e $3 = {e_id = 0, e_name = {bv_len = 0, bv_val = 0x1d13e9d8 ""}, e_nname = {bv_len = 0, bv_val = 0x1d13e9d0 ""}, e_attrs = 0x0, e_ocflags = 288, e_bv = {bv_len = 0, bv_val = 0x0}, e_private = 0x1b765080} --Quanah

1 0

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

07 Oct '08

On 10/7/08, Sylvain THOMAS <sylvain.thomas(a)gmail.com> wrote: > On 10/3/08, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: >> >> Can you: >> >> (a) reproduce with the current RE24 source? >> (b) Can you provide your slapd.conf files? >> >> Thanks, >> Quanah >> > > Yes. I confirm that I reproduce the problem with the HEAD extracted on > monday 6 october (yesterday). > The configuration and environment are the same as ITS 5661 (see > followup 3 of that ITS), but here I do not use the mirrormode. > Thanks and best regards > Sylvain Thomas > I would like to add that if you modify the script test018-syncreplication-persist in order to import two different ldif files in parallel the same problem occurs from time to time. The error message is : Filtering producer results... Filtering consumer results... Comparing retrieved entries from producer and consumer... test failed - producer and consumer databases differ I think this is a serious data integrity problem in the replication process. The weakness of the test018 is that it does not test simultaneous import of data. Best Regards Sylvain Thomas

1 0

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

07 Oct '08

On 10/3/08, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > > Can you: > > (a) reproduce with the current RE24 source? > (b) Can you provide your slapd.conf files? > > Thanks, > Quanah > Yes. I confirm that I reproduce the problem with the HEAD extracted on monday 6 october (yesterday). The configuration and environment are the same as ITS 5661 (see followup 3 of that ITS), but here I do not use the mirrormode. Thanks and best regards Sylvain Thomas

1 0

Re: (ITS#5728) back-bdb should release entries before writing to network
by h.b.furuseth＠usit.uio.no 07 Oct '08

07 Oct '08

For reference: There's more about this in ITS#5340. Somewhat confused discussion, unfortunately. -- Hallvard

1 0

Re: (ITS#5340) REP_ENTRY_MODIFIABLE bug in dynlist
by h.b.furuseth＠usit.uio.no 07 Oct '08

07 Oct '08

Belatead followup: This description of REP_ENTRY_MUSTRELEASE was still wrong. See ITS#5728: BDB didn't set the flag, ITS#3671 just gave the impression it would. Also code much take care to call overlay_entry_release_ov() instead of be_entry_release_r() when appropriate, as in ITS#5451. -- Hallvard

1 0

Re: Bug- Enforcing validation when validator is NULL
by Prashant kulkarni 07 Oct '08

07 Oct '08

Thanks Pierangelo And Harpreet for your reply As you suggested as per latest RFC specification , it is good idea for those attributes who don't have validators or where validator are all NULL to remove those attributes from *.schema files and those syntaxes from hardcoded code files. so any idea in which openLDAP release those attributes will be removed from schema and hardcoded code. ? But currently since these attributes are defined and hard coded in openldap code , the problem is I can't re-define in custom schema exactly with same name as "protocol information" as the openldap service will not start I have to define it as protocol informationXXX or something different to make it work but it then it will breaks the schema for our product which we use for other LDAP server also also I am thinking there is another solution to this bug . in openLDAP code in files /servers/slapd/modify.c and entry.C if all the validator are NULL then it should skip the checking for validation and throwing the error "no validator for syntax". in that way openldap will allow to modify/add values for those attributes having all NULL validator without enforcing. if ( ATLEAST ONE VALIDATOR PRESENT) //pseudo codeIS { if( !pretty && !validate ) { *text = "no validator for syntax"; snprintf( textbuf, textlen, "%s: no validator for syntax %s", ml->sml_type.bv_val, ad->ad_type->sat_syntax->ssyn_oid ); *text = textbuf; return LDAP_INVALID_SYNTAX; } Thanks and Regards Prashant Message: 19 Date: Mon, 29 Sep 2008 20:25:14 +0200 From: Pierangelo Masarati <ando(a)sys-net.it<http://mail.google.com/mail/h/xw1gbla4xfz4/?v=b&cs=wh&to=ando@sys-net.it> > Subject: Re: Bug- Enforcing validation when validator is NULL To: Prashant kulkarni <prashantk100(a)gmail.com<http://mail.google.com/mail/h/xw1gbla4xfz4/?v=b&cs=wh&to=prashantk100@gmail…> > Cc: openldap-bugs(a)openldap.org<http://mail.google.com/mail/h/xw1gbla4xfz4/?v=b&cs=wh&to=openldap-bugs@open…> Message-ID: <48E11D8A.7090706(a)sys-net.it<http://mail.google.com/mail/h/xw1gbla4xfz4/?v=b&cs=wh&to=48E11D8A.7090706@s…> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed Prashant kulkarni wrote: > When I am trying to add/edit the value to the attribute "protocol > information" which is required in our schema I am getting the error > > Invalid syntax :protocol information: no validator for syntax > 1.3.6.1.4.1.1466.115.121.1.42 > > from the earlier mailing list I have found The problem seems to be lack of > validations in the schema_init.c source code for attribure 'Protocol > Information' > > this attribute protocolInformation is defined in core.schema > > {"( 1.3.6.1.4.1.1466.115.121.1.42 DESC 'Protocol Information' )", > 0, NULL, NULL, NULL}, This syntax has been removed from RFC 2252 when revised in RFC 4517, as explicitly indicated in notes 21 and 28 to Appendix B of the latter. This because although mentioned in RFC 2252, those syntaxes were not defined and thus posing interoperability problems. I believe OpenLDAP should move one step forward toward RFC 451* compliance by removing (actually, marking as OBSOLETE) those attributes from *.schema files and those syntaxes from hardcoded ones. > including values like dnPretty ,UTF8StringValidate..etc in the code instead > of NULL values will resolve my problem, but then that require the custom > build and I have to do for all the attributes where validation is defined as > NULL. Not entirely true: you could implement a run-time module that looks up those syntaxes and modifies the appropriate pointers right after initialization. Unless significant changes in the related slapd structures or API, your module would seamlessly breeze through minor and even major releases. Furthermore, if those syntaxes are removed from the hardcoded ones, you could define them via a custom schema file using the X-SUBST feature (ITS#5663) recently introduced in HEAD code. It allows to provide a substitute syntax for unimplemented ones. > I personally feel that for those attributes where validation are NULL in > schema_init.c and other schema files, the openLDAP should not force the > validation and give this error message, as all these attributes in which > validation are not defined becomes unusable . > > In Tivoli/Sun and Microsoft Active directory LDAP validation is not enforced > where validation is defined as NULL hence I am not getting these kind of > error in Tivoli/Sun and Microsoft Active directory for editing of this > attribute . > > So any idea how to resolve this ? there is any way to modify any of the > config file in openldap to disable this validation for protocol information > ? > do I have to raise bug request for the same and is this going to be fixed in > next openLDAP release. ? > > Any help and suggestions in this direction is highly appreciated. I personally believe the absence of a validator for those syntaxes is the safest thing OpenLDAP can do to prevent further interoperability issues. The workaround illustrated above should allow you to circumvent your problem without too much harm. Of course, that's my personal opinion, which might differ from that of the OpenLDAP project. 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<http://mail.google.com/mail/h/xw1gbla4xfz4/?v=b&cs=wh&to=ando@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