- openldap-bugs - openldap.org

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

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

16 Jun '11

Full_Name: Ondrej Kuznik Version: master OS: Linux URL: ftp://ftp.openldap.org/incoming/ondrej-kuznik-20110616.patch Submission from: (NULL) (62.168.56.1) There is a minute chance of crashing OpenLDAP when registering a monitor callback while the monitor is dormant. See URL for a suggested patch. The attached file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Acision. Acision has not assigned rights and/or interest in this work to any party. I, Ondrej Kuznik am authorized by Acision, my employer, to release this work under the following terms. The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2010 Acision Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License.

1 0

Re: (ITS#6892) Segfault in Syncprov overlay
by ghola＠rebelbase.com 15 Jun '11

15 Jun '11

I'm unable to reproduce this problem with the latest syncrepl.c from git.

1 0

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

15 Jun '11

--_41ab47cd-3d88-4bfe-b11d-afb7d8b14738_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable sorry=2C I mistyped my email address=2C it should be ctcard(a)hotmail.com = = --_41ab47cd-3d88-4bfe-b11d-afb7d8b14738_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style> </head> <body class=3D'hmmessage'> sorry=2C I mistyped my email address=2C it should be ctcard(a)hotmail.com = </body> </html>= --_41ab47cd-3d88-4bfe-b11d-afb7d8b14738_--

1 0

Fwd: Re: (ITS#6968) Glue objectclass created during Grouper provisioning
by hyc＠symas.com 15 Jun '11

15 Jun '11

User error, closing. -------- Original Message -------- Subject: Re: (ITS#6968) Glue objectclass created during Grouper provisioning Date: Wed, 15 Jun 2011 10:40:32 +0100 From: Mark Cairney <Mark.Cairney(a)ed.ac.uk> To: Howard Chu <hyc(a)symas.com> Hi, > > Then please strip out those attributes and objectclasses and verify that the LDIF file still reproduces the problem. I can't do this at the moment as this system will be going live imminently however I think I've tracked down the root cause of the problem. One of our servers was going to Redhat for it's NTP sync rather than the same local source as the others so it's clock was slightly skewed in relation. The issue now seems to no longer be occuring having thrown some fairly large LDIFs as the server as a test. >> > Just clicking on the link in any web browser. Also using the link with wget. Either way authentication is requested. >> I've moved the zip if you still want to take a look but given the cause I'm happy for the issue to be closed. IMO it was probably premature raising it as a bug but I was advised to on the list! I'll reply to my post on the list with the cause/solution for completeness. Kind regards, Mark -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

(ITS#6973) Problem with sssvlv overlay and ldapsearch
by ctcard＠hotmal.com 14 Jun '11

14 Jun '11

Full_Name: Chris Card Version: 2.4.23 OS: Centos 5.4 URL: Submission from: (NULL) (91.194.158.133) I am running slapd with a bdb back end, and using ldapsearch to query it. My ldapsearch command looks like this: ldapsearch -h localhost -x -b "..........." -D ".........." -w .... -E \!sss=mail:caseIgnoreIA5Match -E \!vlv=0/10/0/10 which returns the first 11 records and then prompts: # search result search: 2 result: 0 Success control: 1.2.840.113556.1.4.474 false MAMKAQA= sortResult: (0) Success control: 2.16.840.1.113730.3.4.10 false MA8CAQACATkCAQAEBOhhowg= vlvResult: pos=0 count=57 context=6GGjCA== (0) Success # numResponses: 12 # numEntries: 11 Press [before/after(/offset/count|:value)] Enter for the next window. Then, when I press Enter ldapsearch outputs the following and exits: # extended LDIF # # LDAPv3 # base <......> with scope subtree # filter: (objectclass=*) # requesting: ALL # with server side sorting critical control # with virtual list view critical control: 0/10/10/57 # # search result search: 3 result: 4 Size limit exceeded # numResponses: 1 If I then try the search again ldapsearch outputs: # extended LDIF # # LDAPv3 # base <......> with scope subtree # filter: (objectclass=*) # requesting: ALL # with server side sorting critical control # with virtual list view critical control: 0/10/0/10 # # search result search: 2 result: 51 Server is busy text: Other sort requests already in progress # numResponses: 1 The "Size limit exceeded" error appears to come from slap_send_search_entry() in result.c: if ( op->ors_slimit >= 0 && rs->sr_nentries >= op->ors_slimit ) { return LDAP_SIZELIMIT_EXCEEDED; } because op->ors_slimit is 0 instead of SLAP_NO_LIMIT (-1). If I do the ldapsearch with an explicit size limit, using the -z flag, e.g. ldapsearch -h localhost -x -b "..........." -D ".........." -w .... -E \!sss=mail:caseIgnoreIA5Match -E \!vlv=0/10/0/10 -z 20 then I don't get the "Size limit exceeded" error, and all the records are output by ldapsearch with a prompt after each set of 11 records, but after all the records have been output there is a different error before ldapsearch exits: # extended LDIF # # LDAPv3 # base <dc=blackspider,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # with server side sorting critical control # with virtual list view critical control: 0/10/60/57 # # search result search: 8 result: 76 Virtual List View error control: 2.16.840.1.113730.3.4.10 false MA8CATICATkCAU0EBHBFIQo= vlvResult: pos=50 count=57 context=cEUhCg== (77) Unknown error # numResponses: 1 and again a subsequent ldapsearch request gets the "Server is busy" error.

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by hyc＠symas.com 14 Jun '11

14 Jun '11

Timo Teräs wrote: > On 06/14/2011 08:24 AM, hyc(a)symas.com wrote: >> On Tue, Jun 14, 2011 at 08:16:18AM +0300, Timo Ter?s wrote: >>> On 06/13/2011 11:56 PM, Howard Chu wrote: >>>> timo.teras(a)iki.fi wrote: >>>>> ITS#6691 seems to be same issue. >>>>> >>>>> I have a patch to fix this. >>>>> >>>>> It's available at: >>>>> http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… >>>>> >>>> Thanks for the patch, now in git master. >>> >>> Good. Though, it would have been polite to credit me as the commit author. >> >> You were credited in the release branch. > > Oh, right. > >> In the future use git format-patch and things like this won't get overlooked. > > I did not have the git tree available on the 64-bit machine I was given > to work with. And at that point I did not even know which version > control you used. You are expected to have read this already before submitting code: http://www.openldap.org/devel/contributing.html -- -- 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#6657) back-sql segfault in backsql_search
by timo.teras＠iki.fi 13 Jun '11

13 Jun '11

On 06/14/2011 08:24 AM, hyc(a)symas.com wrote: > On Tue, Jun 14, 2011 at 08:16:18AM +0300, Timo Ter?s wrote: >> On 06/13/2011 11:56 PM, Howard Chu wrote: >>> timo.teras(a)iki.fi wrote: >>>> ITS#6691 seems to be same issue. >>>> >>>> I have a patch to fix this. >>>> >>>> It's available at: >>>> http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… >>>> >>> Thanks for the patch, now in git master. >> >> Good. Though, it would have been polite to credit me as the commit author. > > You were credited in the release branch. Oh, right. > In the future use git format-patch and things like this won't get overlooked. I did not have the git tree available on the 64-bit machine I was given to work with. And at that point I did not even know which version control you used. git commit does have --author="" switch, so it's very easy to set the patch author properly even if it's not in git patch format.

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by hyc＠symas.com 13 Jun '11

13 Jun '11

On Tue, Jun 14, 2011 at 08:16:18AM +0300, Timo Ter?s wrote: > On 06/13/2011 11:56 PM, Howard Chu wrote: > > timo.teras(a)iki.fi wrote: > >> ITS#6691 seems to be same issue. > >> > >> I have a patch to fix this. > >> > >> It's available at: > >> http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… > >> > > Thanks for the patch, now in git master. > > Good. Though, it would have been polite to credit me as the commit author. You were credited in the release branch. In the future use git format-patch and things like this won't get overlooked. > > Thanks, > Timo

1 0

RE: (ITS#6964) ./configure bug when specifying openssl as the TLS library to use
by the_uhu＠hotmail.com 13 Jun '11

13 Jun '11

--_d1f53d59-c756-486d-94a1-c6fa39a61c52_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C Am wondering what I am missing here? Because to get OpenLDAP to compile wit= h openssl as the TLS library to use=2C I had change this line. You said that line 19408 on your copy of configure is not the LIBS line bel= ow even though I downloaded openldap fresh - could you offer an explanation= please? Paul. From: the_uhu(a)hotmail.com To: openldap-its(a)openldap.org Subject: RE: (ITS#6964) ./configure bug when specifying openssl as the TLS = library to use Date: Thu=2C 9 Jun 2011 00:16:10 +0000 I've just downloaded openldap stable fresh=2C opened up configure and this = is at line 19408 without an if check: LIBS=3D"-lssl -lcrypto -lRSAglue -lrsaref $LIBS" Also checked the source repository on the website and it's there also. Can you please double check? Paul. > Date: Wed=2C 8 Jun 2011 22:13:55 +0000 > From: openldap-its(a)OpenLDAP.org > To: the_uhu(a)hotmail.com > Subject: Re: (ITS#6964) ./configure bug when specifying openssl as the TL= S library to use >=20 > I don't know where your configure script came from=2C but there's nothing= related > to OpenSSL at line 19408 of the current released configure script=2C and = our > script has had logic to detect -lrsaref since 1999. >=20 > Closing this ITS. Use the actual configure script supplied by the OpenLDA= P > Project. = --_d1f53d59-c756-486d-94a1-c6fa39a61c52_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style> </head> <body class=3D'hmmessage'> Hi=2C Am wondering what I am missing here? Because to get OpenLDAP t= o compile with openssl as the TLS library to use=2C I had change this line.= You said that line 19408 on your copy of configure is not the LIBS = line below even though I downloaded openldap fresh - could you offer an exp= lanation please? Paul. <hr id=3D"stopSpelling">From: the_uhu@= hotmail.com To: openldap-its(a)openldap.org Subject: RE: (ITS#6964) ./c= onfigure bug when specifying openssl as the TLS library to use Date: Thu= =2C 9 Jun 2011 00:16:10 +0000 <meta http-equiv=3D"Content-Type" content=3D"text/html=3B charset=3Dunicode= "> <meta name=3D"Generator" content=3D"Microsoft SafeHTML"> <style> .ExternalClass .ecxhmmessage P {padding:0px=3B} .ExternalClass body.ecxhmmessage {font-size:10pt=3Bfont-family:Tahoma=3B} </style> I've just downloaded openldap stable fresh=2C opened up configure and this = is at line 19408 without an if check: LIBS=3D"-lssl -lcrypto -lRSAgl= ue -lrsaref $LIBS" Also checked the source repository on the website= and it's there also. Can you please double check? Paul. <= br> &gt=3B Date: Wed=2C 8 Jun 2011 22:13:55 +0000 &gt=3B From: openld= ap-its(a)OpenLDAP.org &gt=3B To: the_uhu(a)hotmail.com &gt=3B Subject: Re= : (ITS#6964) ./configure bug when specifying openssl as the TLS library to = use &gt=3B &gt=3B I don't know where your configure script came from= =2C but there's nothing related &gt=3B to OpenSSL at line 19408 of the c= urrent released configure script=2C and our &gt=3B script has had logic = to detect -lrsaref since 1999. &gt=3B &gt=3B Closing this ITS. Use t= he actual configure script supplied by the OpenLDAP &gt=3B Project. = </body> </html>= --_d1f53d59-c756-486d-94a1-c6fa39a61c52_--

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by hyc＠symas.com 13 Jun '11

13 Jun '11

timo.teras(a)iki.fi wrote: > ITS#6691 seems to be same issue. > > I have a patch to fix this. > > It's available at: > http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… > > - Timo > > > Thanks for the patch, now in git 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#6971) Incorrect configure option in documentation
by quanah＠zimbra.com 13 Jun '11

13 Jun '11

--On Sunday, June 12, 2011 4:15 AM +0000 crhea(a)mayo.edu wrote: > Full_Name: Cris Rhea > Version: 2.4.25 > OS: Linux/CentOS > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (129.176.151.29) > > > http://www.openldap.org/doc/admin24/install.html#TCP%20Wrappers > > Sections 4.2.6 and 4.3 mention using "--with-wrappers" to enable TCP > Wrappers. This > option does not cause "configure" to fail, but instead, silently does > nothing. > > The correct option is "--enable-wrappers". > > This is also a minor security bug as people might think their systems have > TCP Wrapper restrictions, but unless someone tests it, they won't realize > it isn't working. > Thanks for the report, this has been fixed in the git master. --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#6972) [PATCH] Autogroup double-free of LDAPURLDesc *lud in autogroup_add_group when the URL contains a filter with >1 attribute.
by gerry＠everythingsucks.co.uk 13 Jun '11

13 Jun '11

--001485f86174bced0304a59d35e3 Content-Type: text/plain; charset=ISO-8859-1 In further testing this patch requires modification, I'll follow up shortly with a fixed up version. G --001485f86174bced0304a59d35e3 Content-Type: text/html; charset=ISO-8859-1 In further testing this patch requires modification, I'll follow up shortly with a fixed up version. G --001485f86174bced0304a59d35e3--

1 0

Re: (ITS#6970) OpenLDAP 2.4.25 MemberOf + AutoGroup user has stale "memberof" attributes for target group after removal from trigger group
by gerry＠everythingsucks.co.uk 13 Jun '11

13 Jun '11

--00163628477eca7fed04a59d338b Content-Type: text/plain; charset=ISO-8859-1 In further testing in our environment we've found this patch to be ineffective. We're seeing lockups consistently when changing other attributes. I'll follow up with more details and some traces shortly (miight try with tip first though :0) G --00163628477eca7fed04a59d338b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable In further testing in our environment we've found this patch to be inef= fective. We're seeing lockups consistently when changing other a= ttributes. I'll follow up with more details and some traces shor= tly (miight try with tip first though :0) G --00163628477eca7fed04a59d338b--

1 0

Re: (ITS#6691) error 4 in slapd: segfault with back-sql in debian amd64
by timo.teras＠iki.fi 13 Jun '11

13 Jun '11

ITS#6657 seems to be same issue. I have a patch to fix this. It's available at: http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… - Timo

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by timo.teras＠iki.fi 13 Jun '11

13 Jun '11

ITS#6691 seems to be same issue. I have a patch to fix this. It's available at: http://git.alpinelinux.org/cgit/aports.git/plain/main/openldap/openldap-bac… - Timo

1 0

(ITS#6972) [PATCH] Autogroup double-free of LDAPURLDesc *lud in autogroup_add_group when the URL contains a filter with >1 attribute.
by gerry＠everythingsucks.co.uk 12 Jun '11

12 Jun '11

Full_Name: Gerry Calderhead Version: OpenLDAP 2.4.25 OS: Linux RHEL5.5 URL: http://uploading.com/files/ad3ecc7f/0001-Autogroup-double-free-of-LDAPURLDe… Submission from: (NULL) (80.238.1.135) We found this issue when we swapped from dynlist to autogroup. Dynlist happily supports pulling over multiple attributes (memberuid and member in our case). When we removed dynlist and added autogroup instead we got an immediate crash because a double-free was picked up by our C library. The code at fault is in autogroup_add_group in the case for was: "to much attributes" now: "too many (%d) attributes" where the lud was free'd then "goto cleanup" was called thus attempting to free it agan. Fix --- The bare-minimum change requried to stop the crash in this case is: File:autogroup.c Function: autogroup_add_group if ( i > 1 ) { Debug( LDAP_DEBUG_ANY, "autogroup_add_group: to much attributes specified in url <%s>\n", bv->bv_val, 0, 0); /* FIXME: error? */ ldap_free_urldesc( lud ); ch_free( agf ); + continue; } I've taken the opportunity to sense-check the other error cases here and hence made the error reporting slightly more useful and eliminated the goto. The git-format-patch, containing the fix above and the clean-up I mentioned is available here: http://uploading.com/files/ad3ecc7f/0001-Autogroup-double-free-of-LDAPURLDe… sha1sum 313f55d01f37a48c5c29ea5232e6343039e6e956 0001-Autogroup-double-free-of-LDAPURLDesc-lud-in-autogrou.patch Public Domain Notice -------------------- I, Gerry Calderhead, 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

(ITS#6971) Incorrect configure option in documentation
by crhea＠mayo.edu 11 Jun '11

11 Jun '11

Full_Name: Cris Rhea Version: 2.4.25 OS: Linux/CentOS URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (129.176.151.29) http://www.openldap.org/doc/admin24/install.html#TCP%20Wrappers Sections 4.2.6 and 4.3 mention using "--with-wrappers" to enable TCP Wrappers. This option does not cause "configure" to fail, but instead, silently does nothing. The correct option is "--enable-wrappers". This is also a minor security bug as people might think their systems have TCP Wrapper restrictions, but unless someone tests it, they won't realize it isn't working.

1 0

Re: (ITS#6970) OpenLDAP 2.4.25 MemberOf + AutoGroup user has stale "memberof" attributes for target group after removal from trigger group
by gerry＠everythingsucks.co.uk 11 Jun '11

11 Jun '11

--001485f8123ed53b6404a5759323 Content-Type: text/plain; charset=ISO-8859-1 Note the "Analysis" section is a copy/paste of the comment from the code. When it says "this response function" it means the function: autogroup_response. G On 11 June 2011 21:24, <openldap-its(a)openldap.org> wrote: > > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#6970. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#6970) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=(ITS#6970) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=6970 > > Please remember to retain your issue tracking number (ITS#6970) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. > > --001485f8123ed53b6404a5759323 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Note the "Analysis" section is a copy/paste of the comment from t= he code. When it says "this response function" it means the fu= nction: autogroup_response. G <div class=3D"gmail_quote">On 11 Ju= ne 2011 21:24, <<a href=3D"mailto:openldap-its@openld= ap.org">openldap-its(a)openldap.org</a>> wrote: <blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde= r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** Thanks for your report to the OpenLDAP Issue Tracking System. =A0Your report has been assigned the tracking number ITS#6970. One of our support engineers will look at your report in due course. Note that this may take some time because our support engineers are volunteers. =A0They only work on OpenLDAP when they have spare time. If you need to provide additional information in regards to your issue report, you may do so by replying to this message. =A0Note that any mail sent to <a href=3D"mailto:openldap-its@openldap.org">openldap-its@= openldap.org</a> with (ITS#6970) in the subject will automatically be attached to the issue report. =A0 =A0 =A0 =A0mailto:<a href=3D"mailto:openldap-its@openldap.org">openlda= p-its(a)openldap.org</a>?subject=3D(ITS#6970) You may follow the progress of this report by loading the following URL in a web browser: =A0 =A0<a href=3D"http://www.OpenLDAP.org/its/index.cgi?findid=3D6970" tar= get=3D"_blank">http://www.OpenLDAP.org/its/index.cgi?findid=3D6970</a> Please remember to retain your issue tracking number (ITS#6970) on any further messages you send to us regarding this report. =A0If you don't then you'll just waste our time and yours because we won't be able to properly track the report. Please note that the Issue Tracking System is not intended to be used to seek help in the proper use of OpenLDAP Software. Such requests will be closed. OpenLDAP Software is user supported. =A0 =A0 =A0 =A0<a href=3D"http://www.OpenLDAP.org/support/" target=3D"_bla= nk">http://www.OpenLDAP.org/support/</a> -------------- Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. </blockquote></div> --001485f8123ed53b6404a5759323--

1 0

(ITS#6970) OpenLDAP 2.4.25 MemberOf + AutoGroup user has stale "memberof" attributes for target group after removal from trigger group
by gerry＠everythingsucks.co.uk 11 Jun '11

11 Jun '11

Full_Name: Gerry Calderhead Version: OpenLDAP 2.4.25 OS: Linux RHEL5.5 URL: http://uploading.com/files/529d29ce/0001-MemberOf-AutoGroup-together-can-le… Submission from: (NULL) (80.238.1.135) What we're trying to do ----------------------- We are using OpenLDAP + GOsa to manage users who have access to an extranet. There are a set of tools on the extranet, let's call then VCS, Bugs, Wiki. The extranet is accessibly by third-parties. We want to delegate some admin to staff in the third parties. The structure we want to use is: Multiple organisations Each organisation has a group per tool, e.g. VCS_access, Bugs_Access, Wiki_Access. Organisation admins can add people to their own groups. We then want to aggregate all people with access to those tools into some top level groups, e.g. all_VCS_access = org1.VCS_access + org2.VCS_access all_Bugs_access = org1.Bugs_access + org2.Bugs_access all_Wiki_access = org1.Wiki_access + org2.Wiki_access It's important to us that when people are added/removed to the organisational groups that the group 'member' attributes and the user's 'memberof' attributes are correct and consistent as these for the basis for our access management. Observed Problem ----------------- If you add a user to a monitored group they are consistently added to the target group. You can now search for them using a memberof filter. If you then remove the user from a monitored group they are consistently removed from the target group. However if you then search for members of the target group using a memberOf filter the removed users always show up. 100% reproducible in our environment. Analysis -------- When using bother AutoGroup + MemberOf the "memberof" attributes are not always deleted when users are removed from a group. The approach this overlay takes to updating the target members list, when a member of a monitored list is removed, is to basically clear the membership and re-populate based on a search. Generally the Autogroup Entry requiring a refresh will be flagged in autogroup_modify_entry function. Within this response function we will then spot these flagged refreshes and will perform the deletes and searches to re-polulate the groups. So far, so simple. However, this response function is not necessarily executing in response context of the original modification (say of a "member") but could be in response to a different modification, specifically the addition of a "memberOf" attribute. i.e. it behaves asynchronously - refreshing the group sometime after the initial change. This is a problem when you wish to use MemberOf and AutoGroup together. 1. Admin removes a "member" of a group 2. AutoGroup spots the removal from a trigger group and flags a refresh on the AutoGroup Entry for the target group. 3. MemberOf overlay's _modify function is called, spots the removal of the "member" and updates the "memberOf" attribute of the trigger group. 4. This response function is called in the context of "memberOf" update 5. We spot the flag on the AGE, and delete all "member"s from the target and initiate searches to re-populate. 6. The MemberOf overlay's _modify function is called in response to the "member" changes in the target group (5). 8. MemberOf's _modify function is guarded against recursion, and exits immediately without removing the "memberof" attributes from the users in the target group. 9. When the search completes all remaining "member"'s will be re-added to the target group. The users will have their "memberOf"'s updated but the chance to remove the dead "memberOf"'s is gone. These will now linger around in the DB. So, the simplest solution I can think of is that we do not make any changes in the context of a modification that may have originated from the MemberOf overlay and instead wait on the next opportunity to trigger the refreshes. In reality if the trigger for the refresh was a "member" change then the refresh will happen during the course of the corresponding _response's - just not on any which modify "memberof". Fix ---- Add the following lines at the start of autogroup_response() if ( op->o_tag == LDAP_REQ_MODIFY ) { Modifications *mz; for ( mz = op->orm_modlist; mz; mz = mz->sml_next ) { if ( mz->sml_mod.sm_desc == agi->agi_memberof_ad ) { Debug(LDAP_DEBUG_TRACE,"==> autogroup_response in context of 'memberof' modification, do nothing!\n", 0, 0, 0); return SLAP_CB_CONTINUE; } } } Full git-format-patch present at URL specified. sha1sum 0001-MemberOf-AutoGroup-together-can-leave-stale-memberof.patch 76c2cf268fff37c0cd744e7b3cfd0afa63d9e991 0001-MemberOf-AutoGroup-together-can-leave-stale-memberof.patch Public Domain Notice -------------------- I, Gerry Calderhead, 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#6892) Segfault in Syncprov overlay
by ghola＠rebelbase.com 10 Jun '11

10 Jun '11

> A patch to avoid this particular crash is now in git master. However, it's still not clear to me why it occurred. Can you get this info from gdb: > frame 1 > print *ss Thanks Howard, here is the info you requested: (gdb) bt #0 test_filter (op=0x40fff7f0, e=0x2aab116ab068, f=0x0) at filterentry.c:69 #1 0x00000000004db315 in syncprov_matchops (op=0x410001b0, opc=0xb096e0, saveit=1) at syncprov.c:1314 #2 0x00000000004db6b5 in syncprov_op_mod (op=0x410001b0, rs=<value optimized out>) at syncprov.c:2124 #3 0x000000000047e62a in overlay_op_walk (op=0x410001b0, rs=0x40ffffc0, which=op_modify, oi=0x8d7ab0, on=0x8dc4f0) at backover.c:659 #4 0x000000000047ec07 in over_op_func (op=0x410001b0, rs=0x40ffffc0, which=op_modify) at backover.c:721 #5 0x000000000047404d in syncrepl_updateCookie (si=0x8d74d0, op=0x410001b0, syncCookie=0x41000b20) at syncrepl.c:3292 #6 0x0000000000478462 in do_syncrep2 (ctx=<value optimized out>, arg=<value optimized out>) at syncrepl.c:1097 #7 do_syncrepl (ctx=<value optimized out>, arg=<value optimized out>) at syncrepl.c:1455 #8 0x00000000004ec5ec in ldap_int_thread_pool_wrapper (xpool=0x84daf0) at tpool.c:685 #9 0x000000301b20673d in start_thread (arg=<value optimized out>) at pthread_create.c:301 #10 0x000000301aad44bd in clone () from /lib64/libc.so.6 (gdb) frame 1 #1 0x00000000004db315 in syncprov_matchops (op=0x410001b0, opc=0xb096e0, saveit=1) at syncprov.c:1314 1314 rc = test_filter( &op2, e, op2.ors_filter ); (gdb) print *ss $1 = {s_next = 0x2aab502177f0, s_base = {bv_len = 16, bv_val = 0x2aab730920e0 "dc=test12,dc=net"}, s_eid = 1, s_op = 0x230ea90, s_rid = 1, s_sid = -1, s_filterstr = {bv_len = 15, bv_val = 0x230f7d0 "(objectClass=*)"}, s_flags = 1, s_inuse = 1, s_res = 0x2aababca90f0, s_restail = 0x2aabc320d920, s_mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 39 times>, __align = 0}}

1 0

(ITS#6969) Need option to show which TLS library is in use
by hyc＠OpenLDAP.org 10 Jun '11

10 Jun '11

Full_Name: Howard Chu Version: 2.4/HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.94.188.8) Submitted by: hyc Now that OpenSSL is not the only TLS library that we support, app developers need a way to check which library is in use. libldap has the info, but due to an oversight it was not exposed. The LDAP_OPT_X_TLS_PACKAGE option has been added to retrieve the TLS implementation name. Currently it may be "OpenSSL", "GnuTLS", or "MozNSS".

1 0

Re: (ITS#6968) Glue objectclass created during Grouper provisioning
by hyc＠symas.com 10 Jun '11

10 Jun '11

Mark.Cairney(a)ed.ac.uk wrote: > Full_Name: Mark Cairney > Version: 2.4.25 > OS: RHEL 5.5 x64 > URL: ftp://ftp.ed.ac.uk/incoming/Mark-Cairney-110610.zip > Submission from: (NULL) (129.215.200.77) > > > During provisioning using Grouper (http://www.internet2.edu/grouper) to populate > a tree of ou and posixGroup objects it looks like the request to create a child > OU is being issued and granted. > This results in the creation of a "ghost" parent OU with the glue objectClass as > documented but syncrepl then constantly tries and fails to provision the ghost > OU to the other servers (as shown in alderlog.txt). Your ftp server is demanding authentication, can't download your file. > My cn=config is listed in cnconfig.txt for reference > > The issue can be reproduced by running Grouper's LDAP provisioner with Grouper > configured to produce a "bushy" structure and it may also be reproduceable if > provisioning via a suitable large LDIF file (grouper.ldif). Sorry, I'm not going to install grouper to test this bug. Please provide scripts to generate data that will reproduce the bug, and please do not use any 3rd party schemas in the data, that just makes it harder to setup a test environment. -- -- 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#6968) Glue objectclass created during Grouper provisioning
by Mark.Cairney＠ed.ac.uk 10 Jun '11

10 Jun '11

Full_Name: Mark Cairney Version: 2.4.25 OS: RHEL 5.5 x64 URL: ftp://ftp.ed.ac.uk/incoming/Mark-Cairney-110610.zip Submission from: (NULL) (129.215.200.77) During provisioning using Grouper (http://www.internet2.edu/grouper) to populate a tree of ou and posixGroup objects it looks like the request to create a child OU is being issued and granted. This results in the creation of a "ghost" parent OU with the glue objectClass as documented but syncrepl then constantly tries and fails to provision the ghost OU to the other servers (as shown in alderlog.txt). My cn=config is listed in cnconfig.txt for reference The issue can be reproduced by running Grouper's LDAP provisioner with Grouper configured to produce a "bushy" structure and it may also be reproduceable if provisioning via a suitable large LDIF file (grouper.ldif).

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs