- openldap-bugs - openldap.org

Re: (ITS#6984) Enable draft-wahl-ldap-session in RE24
by masarati＠aero.polimi.it 04 Jul '11

04 Jul '11

> Full_Name: Michael Ströder > Version: 2.4.x > OS: > URL: > Submission from: (NULL) (84.128.228.27) > > > It seems there is support for draft-wahl-ldap-session in OpenLDAP's source > since > 2007 but it seems not to be enabled in a default build. It's hidden behind > ifdef-statements and one has to use -DLDAP_DEVEL when compiling which is > not > supposed to work with RE24. > > I've tested it with HEAD and I'd be glad this could be enabled for > standard > builds in 2.4 series. As far as I understand, support is complete and conforms to draft as of the time it was implemented. Since the draft expired, it has never been released. Moreover, I sent the author some comments about how the draft could be improved, IMHO, but received no answer (I don't recall whether the discussion was in ldapext or personal, though). If it can be useful, I surely favour its release, provided this complies with the project's policy towards support for expired drafts. p.

1 0

(ITS#6984) Enable draft-wahl-ldap-session in RE24
by michael＠stroeder.com 04 Jul '11

04 Jul '11

Full_Name: Michael Ströder Version: 2.4.x OS: URL: Submission from: (NULL) (84.128.228.27) It seems there is support for draft-wahl-ldap-session in OpenLDAP's source since 2007 but it seems not to be enabled in a default build. It's hidden behind ifdef-statements and one has to use -DLDAP_DEVEL when compiling which is not supposed to work with RE24. I've tested it with HEAD and I'd be glad this could be enabled for standard builds in 2.4 series. Ciao, Michael.

1 0

(ITS#6983) modrdn operations on hdb databases create duplicate return results
by quanah＠zimbra.com 02 Jul '11

02 Jul '11

Full_Name: Quanah Gibson-Mount Version: 2.4.25 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.45.108) When a modrdn operation is done on a subtree (I.e., subtree rename), the result is that back-hdb will return certain entries in that subtree multiple times. Stopping and restarting slapd fixes the behavior. Example: ldapsearch -x -v -H 'ldap://HOST ' -w PASSWORD -D 'uid=zimbra,cn=admins,cn=zimbra' -b "dc=NEWDOMAIN,dc=COM" ldap_initialize( ldap://HOST:389/??base ) filter: (objectclass=*) requesting: All userApplication attributes # extended LDIF # # LDAPv3 # base <dc=NEWDOMAIN,dc=COM> with scope subtree # filter: (objectclass=*) # requesting: ALL # # d-fashion.be dn: dc=NEWDOMAIN,dc=COM o: NEWDOMAIN.com domain zimbraDomainName: NEWDOMAIN.COM zimbraDomainStatus: active zimbraPublicServiceHostname: mail.domain.com zimbraId: affb06b8-79bc-430a-adf7-411cc45e8f00 zimbraMailStatus: enabled objectClass: dcObject objectClass: organization objectClass: zimbraDomain zimbraDomainType: local dc: NEWDOMAIN zimbraPreAuthKey: PRIVATE # people, NEWDOMAIN.COM dn: ou=people,dc=NEWDOMAIN,dc=COM ou: people objectClass: organizationalRole cn: people # people, NEWDOMAIN.COM dn: ou=people,dc=NEWDOMAIN,dc=COM ou: people objectClass: organizationalRole cn: people

1 0

Re: ITS#6873
by masarati＠aero.polimi.it 01 Jul '11

01 Jul '11

> masarati(a)aero.polimi.it wrote: >> Fixed in master, please test. > > Sorry, last message went to wrong ITS. > > But also seems to work now...thanks... :-) > > $ ldapmodify -x -H ldap://localhost:2071 -D > "uid=diradm,ou=schulung,dc=stroeder,dc=local" -e relax -w testsecret -f > authtime_mod.ldif > modifying entry "cn=test1,ou=schulung,dc=stroeder,dc=local" > > -------------------------- authtime_mod.ldif -------------------------- > dn: cn=test1,ou=schulung,dc=stroeder,dc=local > changetype: modify > replace: authTimestamp > authTimestamp: 20110701165029Z Good, I only tested this one. Those were easy fixes, sorry I overlooked them for such a long time. p.

1 0

Re: (ITS#6830) slapo-ppolicy.5 has incorrect schema fragments
by michael＠stroeder.com 01 Jul '11

01 Jul '11

hyc(a)symas.com wrote: > Andrew Findlay wrote: >> On Thu, Jun 09, 2011 at 01:45:17AM -0700, Howard Chu wrote: >> >>> I note that in ppolicy.c we have: >>> >>> { "( 1.3.6.1.4.1.42.2.27.8.1.17 " >>> "NAME ( 'pwdAccountLockedTime' ) " >>> "DESC 'The time an user account was locked' " >>> "EQUALITY generalizedTimeMatch " >>> "ORDERING generalizedTimeOrderingMatch " >>> "SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 " >>> "SINGLE-VALUE " >>> #if 0 >>> /* Not until Relax control is released */ >>> "NO-USER-MODIFICATION " >>> #endif >>> "USAGE directoryOperation )", >>> >>> We have in fact released support for the Relax control, so it's >>> probably time to unifdef these bits and go back to the documented >>> behavior. >> >> That seems reasonable in the long term, though it will break many sites' >> existing password management procedures. The change will have to be >> mentioned in the updated manpage, noting the version at which it takes >> effect. >> >> Should I produce an updated version of the manpage patch? > > Well since you raise the question, what do you think is the more sensible > approach to all of this? I was the one who argued in ldapext that these > attributes should be no-user-modification but perhaps that makes them too > inconvenient to administer. Given the fact that the Relax Rules control still has .666 OID it cannot be used (see my related messages to openldap-devel and ietf-ldapext). At least what's always being said about .666 OIDs... Ciao, Michael.

1 0

Re: ITS#6873
by michael＠stroeder.com 01 Jul '11

01 Jul '11

masarati(a)aero.polimi.it wrote: > Fixed in master, please test. Sorry, last message went to wrong ITS. But also seems to work now...thanks... :-) $ ldapmodify -x -H ldap://localhost:2071 -D "uid=diradm,ou=schulung,dc=stroeder,dc=local" -e relax -w testsecret -f authtime_mod.ldif modifying entry "cn=test1,ou=schulung,dc=stroeder,dc=local" -------------------------- authtime_mod.ldif -------------------------- dn: cn=test1,ou=schulung,dc=stroeder,dc=local changetype: modify replace: authTimestamp authTimestamp: 20110701165029Z

1 0

ITS#6886
by michael＠stroeder.com 01 Jul '11

01 Jul '11

masarati(a)aero.polimi.it wrote: > Fixed in master, please test. Seems to work now...thanks... :-) *** ldap://localhost:2071 - SimpleLDAPObject.extop (('1.3.6.1.4.1.1466.101.119.1', '0/\x80)cn=test1,ou=schulung,dc=stroeder,dc=local\x81\x02\x1c ', None, None),{}) => result: 2 *** ldap://localhost:2071 - SimpleLDAPObject.result4 ((2, 1, -1, 1, 1, 1),{}) => result: (120, [], 2, [], '1.3.6.1.4.1.1466.101.119.1', '0\x04\x81\x02\x1c ') Response TTL: 7200

1 0

Re: ITS#6873
by michael＠stroeder.com 01 Jul '11

01 Jul '11

masarati(a)aero.polimi.it wrote: > Fixed in master, please test. Seems to work now...thanks... :-) *** ldap://localhost:2071 - SimpleLDAPObject.extop (('1.3.6.1.4.1.1466.101.119.1', '0/\x80)cn=test1,ou=schulung,dc=stroeder,dc=local\x81\x02\x1c ', None, None),{}) => result: 2 *** ldap://localhost:2071 - SimpleLDAPObject.result4 ((2, 1, -1, 1, 1, 1),{}) => result: (120, [], 2, [], '1.3.6.1.4.1.1466.101.119.1', '0\x04\x81\x02\x1c ') Response TTL: 7200

1 0

(ITS#6982) libutil md5 incorrect sizeof
by quanah＠OpenLDAP.org 01 Jul '11

01 Jul '11

Full_Name: Quanah Gibson-Mount Version: 2.4.25 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.45.108) Line 188 in liblutil/md5.c is wrong. It has: memset(ctx, '\0', sizeof(ctx)); /* In case it's sensitive */ It should be: memset(ctx, '\0', sizeof(*ctx)); /* In case it's sensitive */

1 0

ITS#6886
by masarati＠aero.polimi.it 30 Jun '11

30 Jun '11

(should be) fixed in master, please test. p.

1 0

ITS#6873
by masarati＠aero.polimi.it 30 Jun '11

30 Jun '11

Fixed in master, please test. p.

1 0

Re: (ITS#6925) [PATCH] Use inet_ntop for server when available
by Pierangelo Masarati 30 Jun '11

30 Jun '11

Please provide patch as a file, not embedded in email. Upload instructions here <http://www.openldap.org/devel/contributing.html#submitting>. p.

1 0

"database monitor" documentation
by Dan Pritts 30 Jun '11

30 Jun '11

Hi, Looking for docs for the monitor datbase backend, i found this: http://www.openldap.org/devel/admin/monitoringslapd.html Like most other database backends, the monitor backend does honor slapd(8) access and other administrative controls. As some monitor information may be sensitive, it is generally recommend access to cn=monitor be restricted to directory administrators and their monitoring agents. Adding an access directive immediately below the database monitor directive is a clear and effective approach for controlling access. For instance, the addition of the following access directive immediately below the database monitor directive restricts access to monitoring information to the specified directory manager. access to * by dn.exact="cn=Manager,dc=example,dc=com by * none I have misunderstood acl and database config before, but I assume that the ACL here is in error, and something like this from slapd-monitor(5) is appropriate: access to dn.subtree="cn=Monitor" by dn.exact="uid=Admin,dc=my,dc=org" write by users read by * none Assuming I'm correct please update the web docs & let me know. thanks! danno -- Dan Pritts, Sr. Systems Engineer Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224

2 1

Re: (ITS#6830) slapo-ppolicy.5 has incorrect schema fragments
by andrew.findlay＠skills-1st.co.uk 30 Jun '11

30 Jun '11

On Thu, Jun 30, 2011 at 03:11:05AM -0700, Howard Chu wrote: > Well since you raise the question, what do you think is the more > sensible approach to all of this? I was the one who argued in > ldapext that these attributes should be no-user-modification but > perhaps that makes them too inconvenient to administer. I think that the best approach would be to make no change in 2.4 code but to flag in the docs that the behaviour will change for 2.5. The NO-USER-MODIFICATION flags have been in draft-behera since 2005, but draft-zeilenga-ldap-relax has only been around since 2007. The latter document says that rules may not be relaxed unless there is a document saying that they may be. pwdAccountLockedTime is not mentioned in draft-zeilenga-ldap-relax and the relax control is not mentioned in draft-behera-ldap-password-policy, so one of those docs needs updating to make the behaviour legal. It would be interesting to survey other LDAP implementations to see how they currently treat the password-policy attributes. This is already a minefield due to uncertainties and variations in the replication process. Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#6830) slapo-ppolicy.5 has incorrect schema fragments
by hyc＠symas.com 30 Jun '11

30 Jun '11

Andrew Findlay wrote: > On Thu, Jun 09, 2011 at 01:45:17AM -0700, Howard Chu wrote: > >> I note that in ppolicy.c we have: >> >> { "( 1.3.6.1.4.1.42.2.27.8.1.17 " >> "NAME ( 'pwdAccountLockedTime' ) " >> "DESC 'The time an user account was locked' " >> "EQUALITY generalizedTimeMatch " >> "ORDERING generalizedTimeOrderingMatch " >> "SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 " >> "SINGLE-VALUE " >> #if 0 >> /* Not until Relax control is released */ >> "NO-USER-MODIFICATION " >> #endif >> "USAGE directoryOperation )", >> >> We have in fact released support for the Relax control, so it's >> probably time to unifdef these bits and go back to the documented >> behavior. > > That seems reasonable in the long term, though it will break many sites' > existing password management procedures. The change will have to be > mentioned in the updated manpage, noting the version at which it takes > effect. > > Should I produce an updated version of the manpage patch? Well since you raise the question, what do you think is the more sensible approach to all of this? I was the one who argued in ldapext that these attributes should be no-user-modification but perhaps that makes them too inconvenient to administer. -- -- 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#6981) slapd crashes when using sssvlv and pcache overlays
by ctcard＠hotmail.com 30 Jun '11

30 Jun '11

Full_Name: Chris Card Version: HEAD as of 28 Jun 2011 OS: centos 5.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (91.194.158.133) I am running slapd with pcache and sssvlv overlays and back-sql backend. With an empty cache, when I do a request like this: ldapsearch -h localhost -x -b "............" -D "............" -w ........ '(o=.....)' -E \!sss=mail:CaseIgnoreIA5Match slapd crashes in pcache_op_cleanup(), line 2369: /* check for malformed entries: attrs with no values */ { Attribute *a = rs->sr_entry->e_attrs; /* <-- HERE */ because rs->sr_entry is NULL. This appears to be because of the call to rs_flush_entry() in result.c line 1408 which sets rs->sr_entry to NULL prior to the call to pcache_op_cleanup(). The relevant part of my slapd.conf looks like this: database sql suffix "......" rootdn "......" rootpw ...... dbname MySQL dbuser ...... subtree_cond "ldap_entries.dn like CONCAT('%',?)" insentry_stmt "INSERT INTO ldap_entries (dn,oc_map_id,parent,keyval) VALUES (?,?,?,?)" has_ldapinfo_dn_ru no baseobject upper_func UPPER autocommit yes overlay pcache pcache bdb 10000 1 50 100 pcacheAttrset 0 * + pcacheTemplate (objectClass=) 0 60 pcacheTemplate (o=) 0 60 ... pcache-directory /var/tmp/cache pcache-cachesize 100 pcache-index objectClass eq,pres overlay sssvlv sssvlv-max 10 sssvlv-maxpercon 5

1 0

Re: (ITS#6830) slapo-ppolicy.5 has incorrect schema fragments
by andrew.findlay＠skills-1st.co.uk 30 Jun '11

30 Jun '11

On Thu, Jun 09, 2011 at 01:45:17AM -0700, Howard Chu wrote: > I note that in ppolicy.c we have: > > { "( 1.3.6.1.4.1.42.2.27.8.1.17 " > "NAME ( 'pwdAccountLockedTime' ) " > "DESC 'The time an user account was locked' " > "EQUALITY generalizedTimeMatch " > "ORDERING generalizedTimeOrderingMatch " > "SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 " > "SINGLE-VALUE " > #if 0 > /* Not until Relax control is released */ > "NO-USER-MODIFICATION " > #endif > "USAGE directoryOperation )", > > We have in fact released support for the Relax control, so it's > probably time to unifdef these bits and go back to the documented > behavior. That seems reasonable in the long term, though it will break many sites' existing password management procedures. The change will have to be mentioned in the updated manpage, noting the version at which it takes effect. Should I produce an updated version of the manpage patch? Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

(ITS#6980) Patch - Mozilla NSS - memleak - have to free the return from SSL_PeerCertificate
by rmeggins＠redhat.com 29 Jun '11

29 Jun '11

Full_Name: Rich Megginson Version: 2.4.25 (current CVS HEAD) OS: RHEL6 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.25-moznss-free-return-of-SSL_P… Submission from: (NULL) (76.113.106.30) In tlsm_auth_cert_handler, we get the peer's cert from the socket using SSL_PeerCertificate. This value is allocated and/or cached. We must destroy it using CERT_DestroyCertificate. These patch files are derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

Re: (ITS#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by hyc＠symas.com 27 Jun '11

27 Jun '11

Ian Puleston wrote: > There is something missing from the fix. I just had a problem where an asynchronous connect was failing and the result was continuous looping with repeated calls to ldap_sasl_bind. > > The problem is that if the connect fails, ldap_int_poll called from ldap_int_check_async_open gets an error and returns -1, and then -1 is returned up the stack ldap_int_check_async_open -> ldap_send_initial_request -> ldap_sasl_bind. But when ldap_sasl_bind gets that -1 return from ldap_send_initial_request it returns ld->ld_errno, and nowhere have we set that. In fact, ld->ld_errno still contains LDAP_X_CONNECTING from when the initial connect was issued, and so ldap_sasl_bind returns LDAP_X_CONNECTING, and that is what leads to the infinite looping that I see. Thanks for the analysis and fix. Now patched in master. In the future please send actual diffs, as noted http://www.openldap.org/devel/contributing.html > What is missing is that in ldap_int_check_async_open this: > > default: > return -1; > > Should be changed to: > > default: > ld->ld_errno = LDAP_CONNECT_ERROR; > return -1; > > Ian -- -- 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#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by ipuleston＠SonicWALL.com 27 Jun '11

27 Jun '11

There is something missing from the fix. I just had a problem where an asynchronous connect was failing and the result was continuous looping with repeated calls to ldap_sasl_bind. The problem is that if the connect fails, ldap_int_poll called from ldap_int_check_async_open gets an error and returns -1, and then -1 is returned up the stack ldap_int_check_async_open -> ldap_send_initial_request -> ldap_sasl_bind. But when ldap_sasl_bind gets that -1 return from ldap_send_initial_request it returns ld->ld_errno, and nowhere have we set that. In fact, ld->ld_errno still contains LDAP_X_CONNECTING from when the initial connect was issued, and so ldap_sasl_bind returns LDAP_X_CONNECTING, and that is what leads to the infinite looping that I see. What is missing is that in ldap_int_check_async_open this: default: return -1; Should be changed to: default: ld->ld_errno = LDAP_CONNECT_ERROR; return -1; Ian

1 0

Re: (ITS#6870) Undefined reference to ber_* with 2.4.24
by jvcelak＠redhat.com 27 Jun '11

27 Jun '11

LDIF functionality is included in libldif, but the interface is not provided (ldif.h is not installed by make install). This happens for RE24 branch, master branch is fine. Patch: ftp://ftp.openldap.org/incoming/jvcelak-20110627-export-ldif-h.patch Jan

1 0

RE: (ITS#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by ipuleston＠SonicWALL.com 24 Jun '11

24 Jun '11

Thanks Howard. I pulled your change out of GIT and tested it, and it works fine for me. However, just as an FYI, this line in open.c results in a "suggest parentheses around && within ||" warning from gcc with the compiler options that we use to compile our OpenLDAP port, and that in turn results in a build failure (since we use -Werror): if (rc == 0 && ld->ld_options.ldo_tls_mode == LDAP_OPT_X_TLS_HARD || strcmp( srv->lud_scheme, "ldaps" ) == 0 ) The parentheses that I had in that line in my patch avoided that. Ian

1 0

Re: (ITS#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by hyc＠symas.com 24 Jun '11

24 Jun '11

Ian Puleston wrote: >> -----Original Message----- >> From: Howard Chu [mailto:hyc@symas.com] >> Sent: Wednesday, June 08, 2011 5:47 PM >> >> I'm pretty sure that this chunk can never do anything useful. >> ... >> The connection has just been created, asynchronously, so there's no way >> that >> the TLS layer was already started when it got here. > > After re-reviewing it I think you are correct. I put that in because I thought there may be a chance that ldap_int_tls_start could get called from ldap_int_open_connection if the connect completed very quickly in the underlying layers. But even if it did there has been no call to ldap_int_poll to check for it having completed. ldap_pvt_connect and then ldap_connect_to_host return -2 to ldap_int_open_connection on an async connect. And the latter then only calls ldap_int_tls_start if rc == 0, so that call will not happen. > >> Also, I suggest that you only check for CONNST_CONNECTING in the >> callers, and do the TLS check in the check function > > Yes, good idea. I guess that the way I have it allows it to start up TLS immediately if using TLS and the connect completes immediately, but if not using TLS it will return LDAP_X_CONNECTING. What you are suggesting means that if not using TLS and the connect completes immediately then it will be able to go ahead and send the request rather than retuning LDAP_X_CONNECTING. > > I will update the fix and supply a new patch shortly. No need, I already committed a fix to git. It is also in RE24. > > Thanks > Ian > > > > > > > -- -- 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#6828) TLS fails to start when LDAP_OPT_CONNECT_ASYNC is used
by ipuleston＠SonicWALL.com 24 Jun '11

24 Jun '11

> -----Original Message----- > From: Howard Chu [mailto:hyc@symas.com] > Sent: Wednesday, June 08, 2011 5:47 PM > > I'm pretty sure that this chunk can never do anything useful. > ... > The connection has just been created, asynchronously, so there's no way > that > the TLS layer was already started when it got here. After re-reviewing it I think you are correct. I put that in because I thought there may be a chance that ldap_int_tls_start could get called from ldap_int_open_connection if the connect completed very quickly in the underlying layers. But even if it did there has been no call to ldap_int_poll to check for it having completed. ldap_pvt_connect and then ldap_connect_to_host return -2 to ldap_int_open_connection on an async connect. And the latter then only calls ldap_int_tls_start if rc == 0, so that call will not happen. > Also, I suggest that you only check for CONNST_CONNECTING in the > callers, and do the TLS check in the check function Yes, good idea. I guess that the way I have it allows it to start up TLS immediately if using TLS and the connect completes immediately, but if not using TLS it will return LDAP_X_CONNECTING. What you are suggesting means that if not using TLS and the connect completes immediately then it will be able to go ahead and send the request rather than retuning LDAP_X_CONNECTING. I will update the fix and supply a new patch shortly. Thanks Ian

1 0

Re: (ITS#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by jvcelak＠redhat.com 24 Jun '11

24 Jun '11

On Friday 24 June 2011 09:11:41, Howard Chu wrote: > >> There is no file ldifutil.c in OpenLDAP 2.4. > >> > >> I don't know what you're testing against, but this bug report appears > >> invalid. Closing. > > > > $ find -name ldifutil.c > > ./libraries/libldap/ldifutil.c > > ./libraries/libldap_r/ldifutil.c > > > > Tested against git master branch. > > Read again what I wrote. There is no file ldifutil.c in OpenLDAP 2.4. git > master is not the same as the 2.4 releases. Ouch, sorry. Then it is fixed only in master, not in RE24 (7cac590). $ ./ldapmodify -a -x -f /tmp/invalid.ldif -d2048 ldif_parse_line: missing ':' after dc=com ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," Segmentation fault (core dumped) (gdb) bt #0 __strcasecmp_l_ssse3 () at ../sysdeps/x86_64/strcmp.S:214 #1 0x000000000040789c in process_ldif_rec (rbuf=0x67464e "objectclass: inetOrgPerson\nobjectclass: organizationalPerson\nobjectclass: person\nobjectclass: top\ncn: B\nsn: B\nuid: B\nmail: b(a)example.org\n", linenum=1) at ldapmodify.c:655 #2 0x00000000004067d5 in main (argc=6, argv=0x7fffffffdd88) at ldapmodify.c:335

1 0

Re: (ITS#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by hyc＠symas.com 24 Jun '11

24 Jun '11

Jan Vcelak wrote: > On Thursday 23 June 2011 22:41:20, Howard Chu wrote: >> jvcelak(a)redhat.com wrote: >>> Full_Name: Jan Vcelak >>> Version: 2.5.25 >> >> There is no OpenLDAP version 2.5. > > This is a typo. I mean 2.4.25. (But it an older issue, it was reported in RH > bugzilla against 2.4.23.) > >> There is no file ldifutil.c in OpenLDAP 2.4. >> >> I don't know what you're testing against, but this bug report appears >> invalid. Closing. > > $ find -name ldifutil.c > ./libraries/libldap/ldifutil.c > ./libraries/libldap_r/ldifutil.c > > Tested against git master branch. Read again what I wrote. There is no file ldifutil.c in OpenLDAP 2.4. git master is not the same as the 2.4 releases. >> Your example doesn't SEGV for me. Anyway, I've committed a different patch >> to master for this issue. > > Strange... Fedora Linux 15, 64bit. And clearly an uninitialized memory was > accessed. But your fix is fine and works for me. > > Thank you. > > Jan > -- -- 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#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by jvcelak＠redhat.com 24 Jun '11

24 Jun '11

On Thursday 23 June 2011 22:41:20, Howard Chu wrote: > jvcelak(a)redhat.com wrote: > > Full_Name: Jan Vcelak > > Version: 2.5.25 > > There is no OpenLDAP version 2.5. This is a typo. I mean 2.4.25. (But it an older issue, it was reported in RH bugzilla against 2.4.23.) > There is no file ldifutil.c in OpenLDAP 2.4. > > I don't know what you're testing against, but this bug report appears > invalid. Closing. $ find -name ldifutil.c ./libraries/libldap/ldifutil.c ./libraries/libldap_r/ldifutil.c Tested against git master branch. > Your example doesn't SEGV for me. Anyway, I've committed a different patch > to master for this issue. Strange... Fedora Linux 15, 64bit. And clearly an uninitialized memory was accessed. But your fix is fine and works for me. Thank you. Jan

1 0

Re: (ITS#6977) ldapwhoami minor verbose bugfix patch submission
by hyc＠symas.com 23 Jun '11

23 Jun '11

hyc(a)symas.com wrote: > checker(a)d6.com wrote: >> Full_Name: Chris Hecker >> Version: 2.4.25 >> OS: centos 5.6 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (98.248.126.162) >> >> >> Hi, ldapwhoami erroneously prints the "Result: Success (0)" string even if -v is >> not specified due to a minor bug in the code. Here is a fix. I am running >> 2.3.43, but just checked the latest repository version and the bug is still >> there (although at line 203 now), so I marked the version above as latest. >> >> Thanks, >> Chris > > It seems to me the better fix would be to change ldap_parse_result() to not > populate matcheddn or text when their values are zero-length. Kurt, any > particular reason things should continue to work as they currently do? OK, they work according to the C API draft. (sigh.) Client tools patched in 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#6977) ldapwhoami minor verbose bugfix patch submission
by checker＠d6.com 23 Jun '11

23 Jun '11

Yeah, I just decided to do the same test as the two enclosed if statements to be 100% compatible. Chris On 2011/06/23 13:31, Howard Chu wrote: > checker(a)d6.com wrote: >> Full_Name: Chris Hecker >> Version: 2.4.25 >> OS: centos 5.6 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (98.248.126.162) >> >> >> Hi, ldapwhoami erroneously prints the "Result: Success (0)" string >> even if -v is >> not specified due to a minor bug in the code. Here is a fix. I am running >> 2.3.43, but just checked the latest repository version and the bug is >> still >> there (although at line 203 now), so I marked the version above as >> latest. >> >> Thanks, >> Chris > > It seems to me the better fix would be to change ldap_parse_result() to > not populate matcheddn or text when their values are zero-length. Kurt, > any particular reason things should continue to work as they currently do? > >> >> --- old/openldap-2.3.43/clients/tools/ldapwhoami.c 2008-02-11 >> 17:24:07.000000000 -0600 >> +++ openldap-2.3.43/clients/tools/ldapwhoami.c 2011-06-21 >> 14:15:28.000000000 >> -0500 >> @@ -215,7 +215,7 @@ >> >> skip: >> if ( verbose || ( code != LDAP_SUCCESS ) || >> - matcheddn || text || refs || ctrls ) >> + (matcheddn&& *matcheddn) || (text&& *text) || refs || ctrls ) >> { >> printf( _("Result: %s (%d)\n"), ldap_err2string( code ), code >> ); >> >> >> > >

1 0

Re: (ITS#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by hyc＠symas.com 23 Jun '11

23 Jun '11

jvcelak(a)redhat.com wrote: > Full_Name: Jan Vcelak > Version: 2.5.25 There is no OpenLDAP version 2.5. > OS: Linux > URL: ftp://ftp.openldap.org/incoming/jvcelak-20110622-ldif-split-indent-segfault… > Submission from: (NULL) (209.132.186.34) > > > Hello, > > input LDIF file with splitted lines which are indented incorrectly causes > SEGFAULT of a client tool. Let me show: > > $ cat /tmp/invalid.ldif > dn: cn=B,dc=my-domain, > dc=com > objectclass: inetOrgPerson > objectclass: organizationalPerson > objectclass: person > objectclass: top > cn: B > sn: B > uid: B > mail: b(a)example.org > > $ ldapmodify -a -x -f /tmp/invalid.ldif -d2048 > ldif_parse_line: missing ':' after dc=com > ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," > Segmentation fault (core dumped) > > > (gdb) bt full > #0 __strcasecmp_l_ssse3 () at ../sysdeps/x86_64/strcmp.S:214 > No locals. > #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, > ctx=0x0) at ldifutil.c:399 There is no file ldifutil.c in OpenLDAP 2.4. I don't know what you're testing against, but this bug report appears invalid. Closing. > fv = 0 > line = 0x668627 "dc=com" > dn = 0x668614 "cn=B,dc=my-domain," > rc = -9 > modop = 0 > expect_modop = 0 > expect_sep = 0 > ldapadd = 1 > new_entry = 1 > delete_entry = 0 > got_all = 0 > pmods = 0x6697e8 > version = 0 > pctrls = 0x0 > i = 1 > j = 0 > k = -1 > idn = 1 > nmods = 1 > bvl = 0x6697f8 > bv = {bv_len = 0, bv_val = 0x0} > __PRETTY_FUNCTION__ = "ldap_parse_ldif_record_x" > #2 0x000000000042e524 in ldap_parse_ldif_record (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1) at > ldifutil.c:565 > No locals. > #3 0x0000000000406ff8 in process_ldif_rec (rbuf=0x668610 "dn", linenum=1) at > ldapmodify.c:404 > lr = {lr_op = 0, lr_dn = {bv_len = 18, bv_val = 0x668614 > "cn=B,dc=my-domain,"}, lr_ctrls = 0x0, ldif_ops = {lr_mods = 0x0, ldif_op_rename > = {lr_newrdn = {bv_len = 0, > bv_val = 0x0}, lr_newsuperior = {bv_len = 0, bv_val = 0x0}, > lr_deleteoldrdn = 0}, ldif_op_ext = {lr_extop_oid = {bv_len = 0, bv_val = 0x0}, > lr_extop_data = { > bv_len = 0, bv_val = 0x0}}, ldif_op_cmp = {lr_cmp_attr = {bv_len > = 0, bv_val = 0x0}, lr_cmp_bvalue = {bv_len = 0, bv_val = 0x0}}}, lr_ctx = 0x0, > lr_lines = 2, > lr_lm = 0x6697d0, lr_mops = 0x0, lr_freeval = 0x6699e0 "", lr_vals = > 0x669930, lr_btype = 0x669880} > lrflags = 1 > rc = 0 > rbuf_bv = {bv_len = 0, > bv_val = 0x66862e "objectclass: inetOrgPerson\nobjectclass: > organizationalPerson\nobjectclass: person\nobjectclass: top\ncn: B\nsn: B\nuid: > B\nmail: b(a)example.org\n"} > #4 0x0000000000406cb7 in main (argc=6, argv=0x7fffffffdd98) at > ldapmodify.c:316 > rbuf = 0x668610 "dn" > rejbuf = 0x0 > rejfp = 0x0 > ldiffp = 0x6600a0 > ldifdummy = {fp = 0x0, prev = 0x0} > matched_msg = 0x448790 "H\211l$\330L\211d$\340H\215-\003\060!" > error_msg = 0x8000<Address 0x8000 out of bounds> > rc = 0 > retval = 0 > ldifrc = 1 > len = 4491152 > i = 0 > lineno = 1 > nextline = 11 > lmax = 4119 > c = {{ldctl_oid = 0x7fe0f05<Address 0x7fe0f05 out of bounds>, > ldctl_value = {bv_len = 5044973646, bv_val = 0x0}, ldctl_iscritical = 0 > '\000'}} > (gdb) frame 1 > #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, > ctx=0x0) at ldifutil.c:399 > 399 if ( !BV_CASEMATCH( lr->lr_btype+i,&bv )) { > (gdb) p *(lr->lr_btype+1) > $1 = {bv_len = 0, bv_val = 0x668627 "dc=com"} > (gdb) > > bv_len is set incorrectly to zero and therefore the string will be compared > against bv, which is a "null string". > > I have uploaded patch to address this issue. > > With the patch applied, the output is following: > > ./ldapmodify -a -x -f /tmp/invalid.ldif -d2048 > ldif_parse_line: missing ':' after dc=com > ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," > > -- -- 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#6977) ldapwhoami minor verbose bugfix patch submission
by hyc＠symas.com 23 Jun '11

23 Jun '11

checker(a)d6.com wrote: > Full_Name: Chris Hecker > Version: 2.4.25 > OS: centos 5.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (98.248.126.162) > > > Hi, ldapwhoami erroneously prints the "Result: Success (0)" string even if -v is > not specified due to a minor bug in the code. Here is a fix. I am running > 2.3.43, but just checked the latest repository version and the bug is still > there (although at line 203 now), so I marked the version above as latest. > > Thanks, > Chris It seems to me the better fix would be to change ldap_parse_result() to not populate matcheddn or text when their values are zero-length. Kurt, any particular reason things should continue to work as they currently do? > > --- old/openldap-2.3.43/clients/tools/ldapwhoami.c 2008-02-11 > 17:24:07.000000000 -0600 > +++ openldap-2.3.43/clients/tools/ldapwhoami.c 2011-06-21 14:15:28.000000000 > -0500 > @@ -215,7 +215,7 @@ > > skip: > if ( verbose || ( code != LDAP_SUCCESS ) || > - matcheddn || text || refs || ctrls ) > + (matcheddn&& *matcheddn) || (text&& *text) || refs || ctrls ) > { > printf( _("Result: %s (%d)\n"), ldap_err2string( code ), code > ); > > > -- -- 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#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by hyc＠symas.com 23 Jun '11

23 Jun '11

jvcelak(a)redhat.com wrote: > Full_Name: Jan Vcelak > Version: 2.5.25 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/jvcelak-20110622-ldif-split-indent-segfault… > Submission from: (NULL) (209.132.186.34) > > > Hello, > > input LDIF file with splitted lines which are indented incorrectly causes > SEGFAULT of a client tool. Let me show: Your example doesn't SEGV for me. Anyway, I've committed a different patch to master for this issue. > > $ cat /tmp/invalid.ldif > dn: cn=B,dc=my-domain, > dc=com > objectclass: inetOrgPerson > objectclass: organizationalPerson > objectclass: person > objectclass: top > cn: B > sn: B > uid: B > mail: b(a)example.org > > $ ldapmodify -a -x -f /tmp/invalid.ldif -d2048 > ldif_parse_line: missing ':' after dc=com > ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," > Segmentation fault (core dumped) > > > (gdb) bt full > #0 __strcasecmp_l_ssse3 () at ../sysdeps/x86_64/strcmp.S:214 > No locals. > #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, > ctx=0x0) at ldifutil.c:399 > fv = 0 > line = 0x668627 "dc=com" > dn = 0x668614 "cn=B,dc=my-domain," > rc = -9 > modop = 0 > expect_modop = 0 > expect_sep = 0 > ldapadd = 1 > new_entry = 1 > delete_entry = 0 > got_all = 0 > pmods = 0x6697e8 > version = 0 > pctrls = 0x0 > i = 1 > j = 0 > k = -1 > idn = 1 > nmods = 1 > bvl = 0x6697f8 > bv = {bv_len = 0, bv_val = 0x0} > __PRETTY_FUNCTION__ = "ldap_parse_ldif_record_x" > #2 0x000000000042e524 in ldap_parse_ldif_record (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1) at > ldifutil.c:565 > No locals. > #3 0x0000000000406ff8 in process_ldif_rec (rbuf=0x668610 "dn", linenum=1) at > ldapmodify.c:404 > lr = {lr_op = 0, lr_dn = {bv_len = 18, bv_val = 0x668614 > "cn=B,dc=my-domain,"}, lr_ctrls = 0x0, ldif_ops = {lr_mods = 0x0, ldif_op_rename > = {lr_newrdn = {bv_len = 0, > bv_val = 0x0}, lr_newsuperior = {bv_len = 0, bv_val = 0x0}, > lr_deleteoldrdn = 0}, ldif_op_ext = {lr_extop_oid = {bv_len = 0, bv_val = 0x0}, > lr_extop_data = { > bv_len = 0, bv_val = 0x0}}, ldif_op_cmp = {lr_cmp_attr = {bv_len > = 0, bv_val = 0x0}, lr_cmp_bvalue = {bv_len = 0, bv_val = 0x0}}}, lr_ctx = 0x0, > lr_lines = 2, > lr_lm = 0x6697d0, lr_mops = 0x0, lr_freeval = 0x6699e0 "", lr_vals = > 0x669930, lr_btype = 0x669880} > lrflags = 1 > rc = 0 > rbuf_bv = {bv_len = 0, > bv_val = 0x66862e "objectclass: inetOrgPerson\nobjectclass: > organizationalPerson\nobjectclass: person\nobjectclass: top\ncn: B\nsn: B\nuid: > B\nmail: b(a)example.org\n"} > #4 0x0000000000406cb7 in main (argc=6, argv=0x7fffffffdd98) at > ldapmodify.c:316 > rbuf = 0x668610 "dn" > rejbuf = 0x0 > rejfp = 0x0 > ldiffp = 0x6600a0 > ldifdummy = {fp = 0x0, prev = 0x0} > matched_msg = 0x448790 "H\211l$\330L\211d$\340H\215-\003\060!" > error_msg = 0x8000<Address 0x8000 out of bounds> > rc = 0 > retval = 0 > ldifrc = 1 > len = 4491152 > i = 0 > lineno = 1 > nextline = 11 > lmax = 4119 > c = {{ldctl_oid = 0x7fe0f05<Address 0x7fe0f05 out of bounds>, > ldctl_value = {bv_len = 5044973646, bv_val = 0x0}, ldctl_iscritical = 0 > '\000'}} > (gdb) frame 1 > #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, > linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, > ctx=0x0) at ldifutil.c:399 > 399 if ( !BV_CASEMATCH( lr->lr_btype+i,&bv )) { > (gdb) p *(lr->lr_btype+1) > $1 = {bv_len = 0, bv_val = 0x668627 "dc=com"} > (gdb) > > bv_len is set incorrectly to zero and therefore the string will be compared > against bv, which is a "null string". > > I have uploaded patch to address this issue. > > With the patch applied, the output is following: > > ./ldapmodify -a -x -f /tmp/invalid.ldif -d2048 > ldif_parse_line: missing ':' after dc=com > ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," > > -- -- 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#6979) test062 portability
by richton＠nbcs.rutgers.edu 23 Jun '11

23 Jun '11

Full_Name: Aaron Richton Version: RE24 OS: irrelevant URL: Submission from: (NULL) (166.217.78.192) It looks like checking the function exit isn't portable; maybe some kind of bash-ism. It looks like the code was on the path to communicating the retval via $RCOUT file already? As such, here's one quick workaround, although I'd love something a bit more elegant: --- test062-config-delete~ 2011-06-23 07:21:01.387583000 -0400 +++ test062-config-delete 2011-06-23 07:21:14.884787000 -0400 @@ -106,7 +106,7 @@ ( $LDAPSEARCH -D cn=config -H $URI1 -y $CONFIGPWF -bcn=config -E \!sync=rp >/dev/null 2>&1 RC=$? - touch $RCOUT + echo $RC > $RCOUT exit $RC ) & @@ -137,7 +137,7 @@ if test -f "$RCOUT" ; then wait $SEARCHPID - SEARCHRC=$? + SEARCHRC=`cat $RCOUT` echo "Checking return code of backgrounded RefreshAndPersist search ..." if test $SEARCHRC != 52 ; then echo "Error: Backgrounded ldapsearch did return the wrong error code: $SEARCHRC"

1 0

(ITS#6978) Invalid indentation of splitted lines in LDIF input file causes SEGFAULT
by jvcelak＠redhat.com 22 Jun '11

22 Jun '11

Full_Name: Jan Vcelak Version: 2.5.25 OS: Linux URL: ftp://ftp.openldap.org/incoming/jvcelak-20110622-ldif-split-indent-segfault… Submission from: (NULL) (209.132.186.34) Hello, input LDIF file with splitted lines which are indented incorrectly causes SEGFAULT of a client tool. Let me show: $ cat /tmp/invalid.ldif dn: cn=B,dc=my-domain, dc=com objectclass: inetOrgPerson objectclass: organizationalPerson objectclass: person objectclass: top cn: B sn: B uid: B mail: b(a)example.org $ ldapmodify -a -x -f /tmp/invalid.ldif -d2048 ldif_parse_line: missing ':' after dc=com ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain," Segmentation fault (core dumped) (gdb) bt full #0 __strcasecmp_l_ssse3 () at ../sysdeps/x86_64/strcmp.S:214 No locals. #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, ctx=0x0) at ldifutil.c:399 fv = 0 line = 0x668627 "dc=com" dn = 0x668614 "cn=B,dc=my-domain," rc = -9 modop = 0 expect_modop = 0 expect_sep = 0 ldapadd = 1 new_entry = 1 delete_entry = 0 got_all = 0 pmods = 0x6697e8 version = 0 pctrls = 0x0 i = 1 j = 0 k = -1 idn = 1 nmods = 1 bvl = 0x6697f8 bv = {bv_len = 0, bv_val = 0x0} __PRETTY_FUNCTION__ = "ldap_parse_ldif_record_x" #2 0x000000000042e524 in ldap_parse_ldif_record (rbuf=0x7fffffffdbb0, linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1) at ldifutil.c:565 No locals. #3 0x0000000000406ff8 in process_ldif_rec (rbuf=0x668610 "dn", linenum=1) at ldapmodify.c:404 lr = {lr_op = 0, lr_dn = {bv_len = 18, bv_val = 0x668614 "cn=B,dc=my-domain,"}, lr_ctrls = 0x0, ldif_ops = {lr_mods = 0x0, ldif_op_rename = {lr_newrdn = {bv_len = 0, bv_val = 0x0}, lr_newsuperior = {bv_len = 0, bv_val = 0x0}, lr_deleteoldrdn = 0}, ldif_op_ext = {lr_extop_oid = {bv_len = 0, bv_val = 0x0}, lr_extop_data = { bv_len = 0, bv_val = 0x0}}, ldif_op_cmp = {lr_cmp_attr = {bv_len = 0, bv_val = 0x0}, lr_cmp_bvalue = {bv_len = 0, bv_val = 0x0}}}, lr_ctx = 0x0, lr_lines = 2, lr_lm = 0x6697d0, lr_mops = 0x0, lr_freeval = 0x6699e0 "", lr_vals = 0x669930, lr_btype = 0x669880} lrflags = 1 rc = 0 rbuf_bv = {bv_len = 0, bv_val = 0x66862e "objectclass: inetOrgPerson\nobjectclass: organizationalPerson\nobjectclass: person\nobjectclass: top\ncn: B\nsn: B\nuid: B\nmail: b(a)example.org\n"} #4 0x0000000000406cb7 in main (argc=6, argv=0x7fffffffdd98) at ldapmodify.c:316 rbuf = 0x668610 "dn" rejbuf = 0x0 rejfp = 0x0 ldiffp = 0x6600a0 ldifdummy = {fp = 0x0, prev = 0x0} matched_msg = 0x448790 "H\211l$\330L\211d$\340H\215-\003\060!" error_msg = 0x8000 <Address 0x8000 out of bounds> rc = 0 retval = 0 ldifrc = 1 len = 4491152 i = 0 lineno = 1 nextline = 11 lmax = 4119 c = {{ldctl_oid = 0x7fe0f05 <Address 0x7fe0f05 out of bounds>, ldctl_value = {bv_len = 5044973646, bv_val = 0x0}, ldctl_iscritical = 0 '\000'}} (gdb) frame 1 #1 0x000000000042d9f3 in ldap_parse_ldif_record_x (rbuf=0x7fffffffdbb0, linenum=1, lr=0x7fffffffdb30, errstr=0x7fffffffe197 "ldapmodify", flags=1, ctx=0x0) at ldifutil.c:399 399 if ( !BV_CASEMATCH( lr->lr_btype+i, &bv )) { (gdb) p *(lr->lr_btype+1) $1 = {bv_len = 0, bv_val = 0x668627 "dc=com"} (gdb) bv_len is set incorrectly to zero and therefore the string will be compared against bv, which is a "null string". I have uploaded patch to address this issue. With the patch applied, the output is following: ./ldapmodify -a -x -f /tmp/invalid.ldif -d2048 ldif_parse_line: missing ':' after dc=com ldapmodify: invalid format (line 2) entry: "cn=B,dc=my-domain,"

1 0

(ITS#6977) ldapwhoami minor verbose bugfix patch submission
by checker＠d6.com 21 Jun '11

21 Jun '11

Full_Name: Chris Hecker Version: 2.4.25 OS: centos 5.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (98.248.126.162) Hi, ldapwhoami erroneously prints the "Result: Success (0)" string even if -v is not specified due to a minor bug in the code. Here is a fix. I am running 2.3.43, but just checked the latest repository version and the bug is still there (although at line 203 now), so I marked the version above as latest. Thanks, Chris --- old/openldap-2.3.43/clients/tools/ldapwhoami.c 2008-02-11 17:24:07.000000000 -0600 +++ openldap-2.3.43/clients/tools/ldapwhoami.c 2011-06-21 14:15:28.000000000 -0500 @@ -215,7 +215,7 @@ skip: if ( verbose || ( code != LDAP_SUCCESS ) || - matcheddn || text || refs || ctrls ) + (matcheddn && *matcheddn) || (text && *text) || refs || ctrls ) { printf( _("Result: %s (%d)\n"), ldap_err2string( code ), code );

1 0

Re: (ITS#6976) Build OpenLDAP on Solaris : error : could not locate usable POSIX Threads
by Howard Chu 21 Jun '11

21 Jun '11

The ITS is for actual bugs in the software. This looks like a misconfiguration in your build environment, not an OpenLDAP bug. You should ask for help on the openldap-technical mailing list instead.

1 0

Re: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by hyc＠symas.com 21 Jun '11

21 Jun '11

ctcard(a)hotmail.com wrote: >> Don't send HTML emails to the ITS.Apologies. >> >> I'm unable to reproduce the error you're talking about. Please provide a >> config that demonstrates the error, and the complete ldapsearch command >> invocation. > The original submission contained the ldapsearch command: > ldapsearch -h localhost -x -b "..........." -D ".........." -w .... -E > \!sss=mail:caseIgnoreIA5Match -E \!vlv=0/10/0/10 I also asked for a server config that demonstrates the problem. When you omit key details, particularly when they are specificly requested, you only slow down the troubleshooting process. From your description in this email, I'm guessing that you've configured sssvlv as a global overlay instead of on a specific database. That's why the overlay is running before fe_op_search. I was testing with the overlay on a specific database. You should probably change your server configuration as a workaround until this gets patched. > (I just suppressed the bind dn, base dn and password) > The important aspect of the search command is that it is doing a server-sidesort on the mail attribute, is asking for a virtual list view, but is letting the size default to zero (which should mean unlimited). >> >> Your patch cannot be correct since limits_check() is already called by the >> frontend at the beginning of every search operation. > > Not in my experience. > As far as I can see limits_check() is called only in fe_op_search() in search.c, and when debugging I found that fe_op_search() was being called from overlay_op_walk() in backover.c. > > When the ldapsearch command is run, it sends a search request to slapd, which returns the first 11 records found, in order of the mail attribute. Then ldapsearch prompts > Press [before/after(/offset/count|:value)] Enter for the next window. > and on hitting enter ldapsearch sends the next request to slapd. This time the request gets handled by sssvlv_op_search() before fe_op_search() is called, because there is an active session. > int overlay_op_walk( Operation *op, SlapReply *rs, slap_operation_t which, slap_overinfo *oi, slap_overinst *on){ BI_op_bind **func; int rc = SLAP_CB_CONTINUE; > for (; on; on=on->on_next ) { func =&on->on_bi.bi_op_bind; if ( func[which] ) { op->o_bd->bd_info = (BackendInfo *)on; rc = func[which]( op, rs ); /*<--- sssvlv_op_search() called here */ if ( rc != SLAP_CB_CONTINUE ) break; } } if ( rc == SLAP_CB_BYPASS ) rc = SLAP_CB_CONTINUE; > func =&oi->oi_orig->bi_op_bind; if ( func[which]&& rc == SLAP_CB_CONTINUE ) { op->o_bd->bd_info = oi->oi_orig; rc = func[which]( op, rs ); /*<--- fe_op_search() called here */ } > Chris -- -- 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#6973) Problem with sssvlv overlay and ldapsearch
by ctcard＠hotmail.com 21 Jun '11

21 Jun '11

> Don't send HTML emails to the ITS.Apologies. > > I'm unable to reproduce the error you're talking about. Please provide a > config that demonstrates the error, and the complete ldapsearch command > invocation. The original submission contained the ldapsearch command: ldapsearch -h localhost -x -b "..........." -D ".........." -w .... -E \!sss=mail:caseIgnoreIA5Match -E \!vlv=0/10/0/10 (I just suppressed the bind dn, base dn and password) The important aspect of the search command is that it is doing a server-sidesort on the mail attribute, is asking for a virtual list view, but is letting the size default to zero (which should mean unlimited). > > Your patch cannot be correct since limits_check() is already called by the > frontend at the beginning of every search operation. Not in my experience. As far as I can see limits_check() is called only in fe_op_search() in search.c, and when debugging I found that fe_op_search() was being called from overlay_op_walk() in backover.c. When the ldapsearch command is run, it sends a search request to slapd, which returns the first 11 records found, in order of the mail attribute. Then ldapsearch prompts Press [before/after(/offset/count|:value)] Enter for the next window. and on hitting enter ldapsearch sends the next request to slapd. This time the request gets handled by sssvlv_op_search() before fe_op_search() is called, because there is an active session. int overlay_op_walk( Operation *op, SlapReply *rs, slap_operation_t which, slap_overinfo *oi, slap_overinst *on){ BI_op_bind **func; int rc = SLAP_CB_CONTINUE; for (; on; on=on->on_next ) { func = &on->on_bi.bi_op_bind; if ( func[which] ) { op->o_bd->bd_info = (BackendInfo *)on; rc = func[which]( op, rs ); /* <--- sssvlv_op_search() called here */ if ( rc != SLAP_CB_CONTINUE ) break; } } if ( rc == SLAP_CB_BYPASS ) rc = SLAP_CB_CONTINUE; func = &oi->oi_orig->bi_op_bind; if ( func[which] && rc == SLAP_CB_CONTINUE ) { op->o_bd->bd_info = oi->oi_orig; rc = func[which]( op, rs ); /* <--- fe_op_search() called here */ } Chris

1 0

(ITS#6976) Build OpenLDAP on Solaris : error : could not locate usable POSIX Threads
by chathuraka.senaratne＠gmail.com 20 Jun '11

20 Jun '11

Full_Name: Samarasooriyage Gayan Chathuraka Senaratne Version: 3 OS: Solaris 64bit URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (202.69.193.78) When I try to configure OpenLDAP on Solaris I get the following error messages. I think I've set the library path environment variable to include the location of libpthread. configure: WARNING: pthread.h: present but cannot be compiled configure: WARNING: pthread.h: check for missing prerequisite headers? configure: WARNING: pthread.h: see the Autoconf documentation configure: WARNING: pthread.h: section "Present But Cannot Be Compiled" configure: WARNING: pthread.h: proceeding with the preprocessor's result configure: WARNING: pthread.h: in the future, the compiler will take precedence configure: WARNING: ## --------------------------------------------- ## configure: WARNING: ## Report this to <http://www.openldap.org/its/> ## configure: WARNING: ## --------------------------------------------- ## checking for pthread.h... yes checking POSIX thread version... 6 checking for LinuxThreads pthread.h... no checking for GNU Pth pthread.h... no checking sched.h usability... yes checking sched.h presence... yes checking for sched.h... yes checking for pthread_create in default libraries... no checking for pthread link with -kthread... no checking for pthread link with -pthread... no checking for pthread link with -pthreads... no checking for pthread link with -mthreads... no checking for pthread link with -thread... no checking for pthread link with -lpthread -lmach -lexc -lc_r... no checking for pthread link with -lpthread -lmach -lexc... no checking for pthread link with -lpthread -Wl,-woff,85... no checking for pthread link with -lpthread... no checking for pthread link with -lc_r... no checking for pthread link with -threads... no checking for pthread link with -lpthreads -lmach -lexc -lc_r... no checking for pthread link with -lpthreads -lmach -lexc... no checking for pthread link with -lpthreads -lexc... no checking for pthread link with -lpthreads... no configure: error: could not locate usable POSIX Threads Please help to solve this. Thanks Gayan

1 0

Re: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by hyc＠symas.com 20 Jun '11

20 Jun '11

ctcard(a)hotmail.com wrote: > --_bbdbd3bd-a986-4f81-a676-3a9863fcc4f3_ > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable Don't send HTML emails to the ITS. I'm unable to reproduce the error you're talking about. Please provide a config that demonstrates the error, and the complete ldapsearch command invocation. Your patch cannot be correct since limits_check() is already called by the frontend at the beginning of every search operation. >> Date: Fri=2C 17 Jun 2011 09:33:22 -0700 >> From: quanah(a)zimbra.com >> To: ctcard(a)hotmail.com=3B openldap-its(a)openldap.org >> Subject: RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch >> =20 >> --On Friday=2C June 17=2C 2011 8:23 AM +0000 ctcard(a)hotmail.com wrote: >> =20 >>> >>> >>>> --On Thursday=2C June 16=2C 2011 5:14 PM +0000 ctcard(a)hotmail.com wrot= > e: >>>> >>>>> >>>>> openldap 2.4.25 is better=2C but still has the LDAP_SIZELIMIT_EXCEED= > ED >>>>> bug.A possible fix is to add a call to limits_check() >>>> >>>> >>>> Please read<http://www.openldap.org/devel/contributing.html> >>>> >>>> Particularly: >>>> >>>> <http://www.openldap.org/devel/contributing.html#patches> >>> Ok=2C patch uploaded to ftp.openldap.org >>> Chris =09 >> =20 >> And the FTP URL for the patch? >> =20 > I uploaded it to the incoming directory on ftp.openldap.org with the name (= > from memory) chris-card-110617.sssvlv.c.patch as per the instructions. > > Chris -- -- 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#6975) Patch - Mozilla NSS - should allow cacertdir in most cases
by rmeggins＠redhat.com 20 Jun '11

20 Jun '11

Full_Name: Rich Megginson Version: 2.4.25 (current CVS HEAD) OS: RHEL6 URL: ftp://ftp.openldap.org/incoming/Mozilla-NSS-should-allow-cacertdir-in-most-… Submission from: (NULL) (76.113.106.30) openldap built with openssl allows most any value of cacertdir - directory is a file, directory does not contain any CA certs, directory does not exist - users expect if they specify TLS_REQCERT=never, no matter what the TLS_CACERTDIR setting is, TLS/SSL will just work. On the other hand, TLS_CACERT failures are hard failures - if TLS_CACERT is specified and is not a valid file, TLS/SSL will fail. These patch files are derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

Re: (ITS#6734) Implment delta-sync based MMR
by hyc＠symas.com 20 Jun '11

20 Jun '11

quanah(a)OpenLDAP.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.23 > OS: NA > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.45.108) > > > To help resolve ITS#6097, it would be helpful to have delta-sync MMR available. > I'm mainly filing this bug for tracking. Experimental support is now in master. A test script is provided but it probably needs to be extended. -- -- 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#6947) ldapadd crashes with LDIFs with invalid line termination
by jvcelak＠redhat.com 20 Jun '11

20 Jun '11

Hello, I have uploaded an updated version of the patch: ftp://ftp.openldap.org/incoming/jvcelak-20110620-ldif-newline-end.patch I found it better to fix the problem in ldif_read_record(), where a similar situation with EOF was already handled. If the line is not terminated by a newline character, it is added. (The previous patch fixed the bug in ldif_countlines() which looks like a blind shot now.) Jan

1 0

RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by ctcard＠hotmail.com 17 Jun '11

17 Jun '11

--_bbdbd3bd-a986-4f81-a676-3a9863fcc4f3_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Date: Fri=2C 17 Jun 2011 09:33:22 -0700 > From: quanah(a)zimbra.com > To: ctcard(a)hotmail.com=3B openldap-its(a)openldap.org > Subject: RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch >=20 > --On Friday=2C June 17=2C 2011 8:23 AM +0000 ctcard(a)hotmail.com wrote: >=20 > > > > > >> --On Thursday=2C June 16=2C 2011 5:14 PM +0000 ctcard(a)hotmail.com wrot= e: > >> > >> > > >> > openldap 2.4.25 is better=2C but still has the LDAP_SIZELIMIT_EXCEED= ED > >> > bug.A possible fix is to add a call to limits_check() > >> > >> > >> Please read <http://www.openldap.org/devel/contributing.html> > >> > >> Particularly: > >> > >> <http://www.openldap.org/devel/contributing.html#patches> > > Ok=2C patch uploaded to ftp.openldap.org > > Chris =09 >=20 > And the FTP URL for the patch? >=20 I uploaded it to the incoming directory on ftp.openldap.org with the name (= from memory) chris-card-110617.sssvlv.c.patch as per the instructions. Chris = --_bbdbd3bd-a986-4f81-a676-3a9863fcc4f3_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style> </head> <body class=3D'hmmessage'><div dir=3D'ltr'> <div>&gt=3B Date: Fri=2C 17 Jun 2011 09:33:22 -0700 &gt=3B From:= quanah(a)zimbra.com &gt=3B To: ctcard(a)hotmail.com=3B openldap-its@openlda= p.org &gt=3B Subject: RE: (ITS#6973) Problem with sssvlv overlay and lda= psearch &gt=3B &gt=3B --On Friday=2C June 17=2C 2011 8:23 AM +0000 c= tcard(a)hotmail.com wrote: &gt=3B &gt=3B &gt=3B &gt=3B &gt=3B &g= t=3B &gt=3B&gt=3B --On Thursday=2C June 16=2C 2011 5:14 PM +0000 ctcard@hot= mail.com wrote: &gt=3B &gt=3B&gt=3B &gt=3B &gt=3B&gt=3B &gt=3B &gt= =3B &gt=3B&gt=3B &gt=3B openldap 2.4.25 is better=2C but still has the LDAP= _SIZELIMIT_EXCEEDED &gt=3B &gt=3B&gt=3B &gt=3B bug.A possible fix is to = add a call to limits_check() &gt=3B &gt=3B&gt=3B &gt=3B &gt=3B&gt=3B<= br>&gt=3B &gt=3B&gt=3B Please read &lt=3Bhttp://www.openldap.org/devel/cont= ributing.html&gt=3B &gt=3B &gt=3B&gt=3B &gt=3B &gt=3B&gt=3B Particula= rly: &gt=3B &gt=3B&gt=3B &gt=3B &gt=3B&gt=3B &lt=3Bhttp://www.openlda= p.org/devel/contributing.html#patches&gt=3B &gt=3B &gt=3B Ok=2C patch up= loaded to ftp.openldap.org &gt=3B &gt=3B Chris &gt=3B &= gt=3B And the FTP URL for the patch? &gt=3B I uploaded it to the inc= oming directory on ftp.openldap.org with the name (from memory) chris-card-= 110617.sssvlv.c.patch as per the instructions. Chris </div> = </div></body> </html>= --_bbdbd3bd-a986-4f81-a676-3a9863fcc4f3_--

1 0

RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by quanah＠zimbra.com 17 Jun '11

17 Jun '11

--On Friday, June 17, 2011 8:23 AM +0000 ctcard(a)hotmail.com wrote: > > >> --On Thursday, June 16, 2011 5:14 PM +0000 ctcard(a)hotmail.com wrote: >> >> > >> > openldap 2.4.25 is better, but still has the LDAP_SIZELIMIT_EXCEEDED >> > bug.A possible fix is to add a call to limits_check() >> >> >> Please read <http://www.openldap.org/devel/contributing.html> >> >> Particularly: >> >> <http://www.openldap.org/devel/contributing.html#patches> > Ok, patch uploaded to ftp.openldap.org > Chris And the FTP URL for the patch? --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by ctcard＠hotmail.com 17 Jun '11

17 Jun '11

> --On Thursday, June 16, 2011 5:14 PM +0000 ctcard(a)hotmail.com wrote: > > > > > openldap 2.4.25 is better, but still has the LDAP_SIZELIMIT_EXCEEDED > > bug.A possible fix is to add a call to limits_check() > > > Please read <http://www.openldap.org/devel/contributing.html> > > Particularly: > > <http://www.openldap.org/devel/contributing.html#patches> Ok, patch uploaded to ftp.openldap.org Chris

1 0

RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by quanah＠zimbra.com 16 Jun '11

16 Jun '11

--On Thursday, June 16, 2011 5:14 PM +0000 ctcard(a)hotmail.com wrote: > > openldap 2.4.25 is better, but still has the LDAP_SIZELIMIT_EXCEEDED > bug.A possible fix is to add a call to limits_check() Please read <http://www.openldap.org/devel/contributing.html> Particularly: <http://www.openldap.org/devel/contributing.html#patches> Submission Formats Submissions should be submitted as a patch suitable for integration into the OpenLDAP Git source repository using git-am(1). Specifically, you should use git-format-patch(1) to construct the patch. Please review patches before submission to ensure only required changes to intended files are included in the patch AND all the intended changes are included in the patch. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

RE: (ITS#6973) Problem with sssvlv overlay and ldapsearch
by ctcard＠hotmail.com 16 Jun '11

16 Jun '11

openldap 2.4.25 is better, but still has the LDAP_SIZELIMIT_EXCEEDED bug.A possible fix is to add a call to limits_check() in sssvlv_op_search() (sssvlv.c) : --- sssvlv.c 2011-03-24 02:04:28.000000000 +0000+++ sssvlv.c.new 2011-06-16 18:07:36.000000000 +0100@@ -839,6 +839,7 @@ sess_id = find_session_by_context( si->svi_max_percon, op->o_conn->c_conn_idx, vc ? vc->vc_context : NO_VC_CONTEXT, ps ? ps->ps_cookie : NO_PS_COOKIE ); if ( sess_id >= 0 ) { so = sort_conns[op->o_conn->c_conn_idx][sess_id];+ limits_check( op, rs ); /* Is it a continuation of a VLV search? */ if ( !vc || so->so_vlv <= SLAP_CONTROL_IGNORED || vc->vc_context != so->so_vcontext ) {

1 0

Re: (ITS#6878) ppcache segfault with tavl_delete
by tjgates＠castlebranch.com 16 Jun '11

16 Jun '11

This is a multi-part message in MIME format. --------------050208080705010102070004 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I can't get this to crash under valgrind, just like it wont crash when run in debug mode. There were a few nasty messages however so I've attached the output from it thus far. -- Tyler Gates Systems Administrator Castle Branch Inc. 910-815-3880 ext 7230 tjgates(a)castlebranch.com This e-mail message, including any attachments, may contain private, confidential, and privileged information for the restricted use of the intended recipient(s). If you are not the intended recipient(s), you may NOT use, disclose, copy, or disseminate this information. Please notify the sender by return e-mail of this misdirected correspondence and destroy all copies of the original message including all attachments. Your cooperation is appreciated. --------------050208080705010102070004 Content-Type: text/plain; name="slapd.valgrind.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="slapd.valgrind.txt" ==25268== Memcheck, a memory error detector ==25268== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==25268== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==25268== Command: /usr/sbin/slapd -h ldap:///\ ldapi:///\ ldaps:/// -g openldap -u openldap -F /etc/ldap/slapd.d ==25268== Parent PID: 25106 ==25268== ==25268== ==25268== HEAP SUMMARY: ==25268== in use at exit: 682,293 bytes in 14,370 blocks ==25268== total heap usage: 47,421 allocs, 33,051 frees, 8,849,431 bytes allocated ==25268== ==25268== LEAK SUMMARY: ==25268== definitely lost: 199 bytes in 6 blocks ==25268== indirectly lost: 13,619 bytes in 450 blocks ==25268== possibly lost: 32,944 bytes in 10 blocks ==25268== still reachable: 635,531 bytes in 13,904 blocks ==25268== suppressed: 0 bytes in 0 blocks ==25268== Rerun with --leak-check=full to see details of leaked memory ==25268== ==25268== For counts of detected and suppressed errors, rerun with: -v ==25268== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 134 from 14) ==25273== Thread 4: ==25273== Conditional jump or move depends on uninitialised value(s) ==25273== at 0x49A249F: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x49A3310: __log_put (in /usr/lib/libdb-4.8.so) ==25273== by 0x494E6F7: __db_addrem_log (in /usr/lib/libdb-4.8.so) ==25273== by 0x495CEB6: __db_pitem (in /usr/lib/libdb-4.8.so) ==25273== by 0x48AEAB3: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x48B0447: __bam_iitem (in /usr/lib/libdb-4.8.so) ==25273== by 0x48A9889: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x4955D0D: __dbc_iput (in /usr/lib/libdb-4.8.so) ==25273== by 0x495817C: __dbc_put (in /usr/lib/libdb-4.8.so) ==25273== by 0x495EBE7: __dbc_put_pp (in /usr/lib/libdb-4.8.so) ==25273== by 0x5493825: hdb_idl_insert_key (idl.c:876) ==25273== by 0x548A5E8: hdb_key_change (key.c:93) ==25273== ==25273== Syscall param pwrite64(buf) points to uninitialised byte(s) ==25273== at 0x4C1AC0B: pwrite64 (pwrite64.c:54) ==25273== by 0x49B9AB7: __os_io (in /usr/lib/libdb-4.8.so) ==25273== by 0x49A11DA: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x49A1E7E: __log_flush_int (in /usr/lib/libdb-4.8.so) ==25273== by 0x49A376C: __log_put (in /usr/lib/libdb-4.8.so) ==25273== by 0x49C8AEA: __txn_regop_log (in /usr/lib/libdb-4.8.so) ==25273== by 0x49C5784: __txn_commit (in /usr/lib/libdb-4.8.so) ==25273== by 0x49C5850: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x54820B7: hdb_modify (modify.c:670) ==25273== by 0x54B0257: merge_entry (pcache.c:874) ==25273== by 0x54B7FFB: cache_entries (pcache.c:2291) ==25273== by 0x54B83EC: pcache_op_cleanup (pcache.c:2396) ==25273== Address 0x6e254b4 is not stack'd, malloc'd or (recently) free'd ==25273== ==25273== Thread 3: ==25273== Conditional jump or move depends on uninitialised value(s) ==25273== at 0x49A249F: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x49A3310: __log_put (in /usr/lib/libdb-4.8.so) ==25273== by 0x494E6F7: __db_addrem_log (in /usr/lib/libdb-4.8.so) ==25273== by 0x495CBE0: __db_ditem (in /usr/lib/libdb-4.8.so) ==25273== by 0x48AB7EE: __bam_ditem (in /usr/lib/libdb-4.8.so) ==25273== by 0x48AA39D: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x48AACFD: ??? (in /usr/lib/libdb-4.8.so) ==25273== by 0x49546C6: __dbc_close (in /usr/lib/libdb-4.8.so) ==25273== by 0x495FC62: __dbc_close_pp (in /usr/lib/libdb-4.8.so) ==25273== by 0x5492ED7: hdb_idl_delete_key (idl.c:1034) ==25273== by 0x548A533: hdb_key_change (key.c:97) ==25273== by 0x5489AD4: indexer (index.c:214) ==25273== ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Thread 4: ==25273== Invalid read of size 4 ==25273== at 0x486C562: ??? (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x486AEBE: ??? (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x486B1BE: ldap_int_tls_start (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x483ECB7: ldap_int_open_connection (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x48570A5: ldap_new_connection (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x483EA78: ldap_open_defconn (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x485855F: ldap_send_initial_request (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x484A929: ldap_sasl_bind (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x545C877: ldap_back_dobind_int (bind.c:1482) ==25273== by 0x545D43D: ldap_back_retry (bind.c:2004) ==25273== by 0x54584A2: ldap_back_search (search.c:530) ==25273== by 0x1BAF5A: overlay_op_walk (backover.c:669) ==25273== Address 0x5ff6524 is 132 bytes inside a block of size 452 free'd ==25273== at 0x4824B3A: free (vg_replace_malloc.c:366) ==25273== by 0x4880C1F: ber_memfree_x (in /usr/lib/liblber-2.4.so.2.7.0) ==25273== by 0x484CEFE: ldap_ld_free (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x484CFB7: ldap_unbind_ext (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x545D3C8: ldap_back_retry (bind.c:1984) ==25273== by 0x54584A2: ldap_back_search (search.c:530) ==25273== by 0x1BAF5A: overlay_op_walk (backover.c:669) ==25273== by 0x1BBC87: over_op_func (backover.c:721) ==25273== by 0x143A83: fe_op_search (search.c:372) ==25273== by 0x144416: do_search (search.c:217) ==25273== by 0x1408C3: connection_operation (connection.c:1113) ==25273== by 0x1413C1: connection_read_thread (connection.c:1249) ==25273== ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Thread 3: ==25273== Conditional jump or move depends on uninitialised value(s) ==25273== at 0x486C56A: ??? (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x486AEBE: ??? (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x486B1BE: ldap_int_tls_start (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x483ECB7: ldap_int_open_connection (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x48570A5: ldap_new_connection (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x483EA78: ldap_open_defconn (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x485855F: ldap_send_initial_request (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x484A929: ldap_sasl_bind (in /usr/lib/libldap_r-2.4.so.2.7.0) ==25273== by 0x545C877: ldap_back_dobind_int (bind.c:1482) ==25273== by 0x545D43D: ldap_back_retry (bind.c:2004) ==25273== by 0x54584A2: ldap_back_search (search.c:530) ==25273== by 0x1BAF5A: overlay_op_walk (backover.c:669) ==25273== ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() ==25273== Warning: invalid file descriptor -1 in syscall write() --------------050208080705010102070004--

1 0

Re: (ITS#6974) Possible segfault in back-monitor
by ondrej.kuznik＠acision.com 16 Jun '11

16 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/16/2011 11:23 AM, openldap-its(a)OpenLDAP.org wrote: > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** Also, in the same file, there are superfluous asserts (assert for a non-null pointer after dereferencing that same pointer) at lines 1233 and 1370. They might be considered documentation, though. - -- Ondrej Kuznik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk35zF0ACgkQ9GWxeeH+cXsIpACglIHvpX9HCWeNL9k6/d7fn9DJ 3I8AnAuxriR7HbUTjRGFXw/qo49tEZPV =Jb1D -----END PGP SIGNATURE----- This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs