- openldap-bugs - openldap.org

Re: (ITS#7503) slapcat: retry a few times when retrieving an entry
by quanah＠zimbra.com 27 Jan '13

27 Jan '13

--On Friday, January 25, 2013 10:26 PM +0000 balint(a)balintreczey.hu wrote: > Full_Name: Balint Reczey > Version: master > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (84.0.168.17) Hi Balint, The patch as submitted is rejected, due to the fact that it changes slapadd, rather than fixing back-bdb/hdb, which is where the actual problem occurs. I.e., your change is too broad. Feel free to submit an updated patch correctly updating the back-bdb/hdb code rather than slapadd. Thanks, 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#7501) added TCP keepalive support to back_ldap
by quanah＠zimbra.com 27 Jan '13

27 Jan '13

--On Thursday, January 24, 2013 4:16 PM +0000 tedcheng(a)symas.com wrote: > > On Jan 24, 2013, at 5:32 AM, Howard Chu wrote: > >> tedcheng(a)symas.com wrote: >>> Full_Name: Ted C. Cheng >>> Version: master >>> OS: Linux/Solaris >>> URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch >>> Submission from: (NULL) (76.174.253.197) Hi Ted, This has been applied to HEAD and RE24, but it has exposed two issues. 1) This has broken back-ldap with dynamic configuration 2) back-meta should be updated to support this parameter as well. Can you please supply an updated patch based off current RE24 and HEAD addressing these two issues. Thanks! --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

(ITS#7505) liblmdb can fail with MDB_PAGE_FULL on a delete
by hyc＠OpenLDAP.org 27 Jan '13

27 Jan '13

Full_Name: Howard Chu Version: RE24/master OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (78.155.233.73) Submitted by: hyc This is the last remaining FIXME in liblmdb/mdb.c... mdb_rebalance() is always called after a delete operation. If the tree needs balancing and it needs to move a node from one page to its sibling, the parent page's separator keys will need updating. If the new separator key is larger than the old one, it may not fit into the parent page, and mdb_update_key() will return MDB_PAGE_FULL. Instead of giving up, mdb_update_key() should invoke mdb_page_split() to make room for the new key.

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by michael＠stroeder.com 26 Jan '13

26 Jan '13

Any chance to see this patch appear in 2.4.34? Ciao, Michael.

1 0

(ITS#7504) document slapcat exit codes in man page
by balint＠balintreczey.hu 25 Jan '13

25 Jan '13

Full_Name: Balint Reczey Version: master OS: Linux URL: http://rbalint.cs.bme.hu/0002-document-slapcat-exit-codes-in-man-page.patch Submission from: (NULL) (84.0.168.17) Slapcat's exit value was undocumented, this patch aims to fix that. Copyright 2013 Balint Reczey <balint(a)balintreczey.hu> Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License.

1 0

(ITS#7503) slapcat: retry a few times when retrieving an entry
by balint＠balintreczey.hu 25 Jan '13

25 Jan '13

Full_Name: Balint Reczey Version: master OS: Linux URL: http://rbalint.cs.bme.hu/0001-slapcat-retry-a-few-times-when-retrieving-an-… Submission from: (NULL) (84.0.168.17) From: Axel Beckert <beckert(a)phys.ethz.ch> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: slapd: slapcat output truncated every now and then Date: Tue, 15 May 2012 18:33:57 +0200 Package: slapd Severity: grave Version: 2.4.23-7.2 Justification: Causes data loss Every now and then slapcat's output does not contain the whole content of the LDAP but is truncated at some LDIF entry border (i.e. all printed LDIF records seem complete). To reproduce run "while sleep 1; do slapcat | wc; done" on a moderately busy LDAP server (writes every few seconds to minutes; about 10000 entries) while slapd is running and notice the occasionally occurring huge change in wc's printed values, e.g.: # while sleep 1; do slapcat | wc; done 471698 1015498 15336677 471698 1015498 15336677 471698 1015498 15336677 ... 471698 1015497 15336635 471698 1015497 15336635 281829 606820 8632165 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336635 308627 664573 9476751 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336637 Please see email thread starting at http://www.openldap.org/lists/openldap-technical/201301/msg00195.html The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2013 Balint Reczey <balint(a)balintreczey.hu> Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License.

1 0

(ITS#7502) slapcat: retry a few times when retrieving an entry
by balint＠balintreczey.hu 25 Jan '13

25 Jan '13

Full_Name: Balint Reczey Version: master OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.0.168.17) From: Axel Beckert <beckert(a)phys.ethz.ch> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: slapd: slapcat output truncated every now and then Date: Tue, 15 May 2012 18:33:57 +0200 Package: slapd Severity: grave Version: 2.4.23-7.2 Justification: Causes data loss Every now and then slapcat's output does not contain the whole content of the LDAP but is truncated at some LDIF entry border (i.e. all printed LDIF records seem complete). To reproduce run "while sleep 1; do slapcat | wc; done" on a moderately busy LDAP server (writes every few seconds to minutes; about 10000 entries) while slapd is running and notice the occasionally occurring huge change in wc's printed values, e.g.: # while sleep 1; do slapcat | wc; done 471698 1015498 15336677 471698 1015498 15336677 471698 1015498 15336677 ... 471698 1015497 15336635 471698 1015497 15336635 281829 606820 8632165 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336635 308627 664573 9476751 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336637 Please see email thread starting at http://www.openldap.org/lists/openldap-technical/201301/msg00195.html

1 0

Re: (ITS#7499)
by benintechnologies＠yahoo.fr 25 Jan '13

25 Jan '13

Le 25/01/2013 15:59, Howard Chu a écrit : > Benin Technologies wrote: >> i was just testing back-sql, so my slapd.conf is basically the one >> that's shipped with openldap, as in >> "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf > > OK, found the bug, fixed now in master. YEP, just tested it, it works. Many thanks !

1 0

Re: (ITS#7499)
by hyc＠symas.com 25 Jan '13

25 Jan '13

Benin Technologies wrote: > i was just testing back-sql, so my slapd.conf is basically the one > that's shipped with openldap, as in > "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf OK, found the bug, fixed now in master. > Le 24/01/2013 20:00, Howard Chu a écrit : >> Benin Technologies wrote: >>> Le 24/01/2013 13:31, Howard Chu a écrit : >>>> Ah. In that case the fix must still be wrong. (Sorry, I'm patching >>>> this blind as I don't have any current SQL installation to test with.) >> >>> OK let me know when you fixed it, it the meantime I'll switch back to >>> slapd.conf >> >> Can you please include your slapd.conf here in this ITS? -- -- 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#7499)
by benintechnologies＠yahoo.fr 24 Jan '13

24 Jan '13

i was just testing back-sql, so my slapd.conf is basically the one that's shipped with openldap, as in "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf I just changed a few parameters, like the pid and argfile directory, odbc and database parameters here it is include /usr/local/etc/openldap/schema/core.schema include /usr/local/etc/openldap/schema/cosine.schema include /usr/local/etc/openldap/schema/inetorgperson.schema # Define global ACLs to disable default read access. pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args ####################################################################### # sql database definitions ####################################################################### database sql suffix "dc=example,dc=com" rootdn "cn=root,dc=example,dc=com" rootpw secret dbname LdapTest dbuser ldaptest dbpasswd ldaptest insentry_stmt "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" upper_func "upper" strcast_func "text" concat_pattern "?||?" has_ldapinfo_dn_ru no Le 24/01/2013 20:00, Howard Chu a écrit : > Benin Technologies wrote: >> Le 24/01/2013 13:31, Howard Chu a écrit : >>> Ah. In that case the fix must still be wrong. (Sorry, I'm patching >>> this blind as I don't have any current SQL installation to test with.) > >> OK let me know when you fixed it, it the meantime I'll switch back to >> slapd.conf > > Can you please include your slapd.conf here in this ITS? >

1 0

Re: (ITS#7499)
by hyc＠symas.com 24 Jan '13

24 Jan '13

Benin Technologies wrote: > Le 24/01/2013 13:31, Howard Chu a écrit : >> Ah. In that case the fix must still be wrong. (Sorry, I'm patching >> this blind as I don't have any current SQL installation to test with.) > OK let me know when you fixed it, it the meantime I'll switch back to > slapd.conf Can you please include your slapd.conf here in this ITS? -- -- 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#7499)
by benintechnologies＠yahoo.fr 24 Jan '13

24 Jan '13

Le 24/01/2013 13:31, Howard Chu a écrit : > Benin Technologies wrote: >> Yes the fix worked (I downloaded the latest openldap.tar.gz on your >> gitweb and installed it). Now slapd starts after having converted to >> cn=config >> >> But after the conversion my ldapsearch returns an 80 error (with >> slapd.conf it worked, the data from PostgreSQL where returned) >> Thus my question : are there other steps to be taken after the >> conversion (all I did was : slaptest -f slapd.conf -F slapd.d) > > Ah. In that case the fix must still be wrong. (Sorry, I'm patching > this blind as I don't have any current SQL installation to test with.) > OK let me know when you fixed it, it the meantime I'll switch back to slapd.conf Thanks BT

1 0

Re: (ITS#7501) added TCP keepalive support to back_ldap
by tedcheng＠symas.com 24 Jan '13

24 Jan '13

On Jan 24, 2013, at 5:32 AM, Howard Chu wrote: > tedcheng(a)symas.com wrote: >> Full_Name: Ted C. Cheng >> Version: master >> OS: Linux/Solaris >> URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch >> Submission from: (NULL) (76.174.253.197) >> >> >> >> Please find in the URL a patch that adds TCP keepalive support to back_ldap. >> >> Please review and apply the patch. > > Note - constructs like "#if 0" are only used for tentative/experimental changes. For patches intended to be released to the public, just delete the blocked out lines. > "#if 0" seems to be a common practice in the code. I only removed the one in the patch. Please find in the link below. https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch Ted C. Cheng Symas Corporation

1 0

Re: (ITS#7501) added TCP keepalive support to back_ldap
by hyc＠symas.com 24 Jan '13

24 Jan '13

tedcheng(a)symas.com wrote: > Full_Name: Ted C. Cheng > Version: master > OS: Linux/Solaris > URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch > Submission from: (NULL) (76.174.253.197) > > > > Please find in the URL a patch that adds TCP keepalive support to back_ldap. > > Please review and apply the patch. Note - constructs like "#if 0" are only used for tentative/experimental changes. For patches intended to be released to the public, just delete the blocked out lines. -- -- 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#7496) Segemtation fault in mdb_entry_decode
by meike.stone＠googlemail.com 24 Jan '13

24 Jan '13

>> Thread 1 (Thread 0x7f738b21c700 (LWP 19394)): > > >> #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at >> search.c:720 >> scopeok = 1 >> edata = {mv_size = 0, mv_data = 0x7f74bbb99728} > > > This indicates that the entry being debugged is actually zero bytes, i.e. > it's not a valid entry at all. Nodes like this get stored in the database > during slapadd when a child entry gets added before its parent; a zero-byte > stub is stored as a placeholder for the missing parent. > When you ran slapadd > you should have seen warning messages about missing entries, telling you > that your LDIF is incomplete. Yes you are right, I repeated the import via slapcat to test and got this error message: ~ # slapadd -w -q -f /etc/openldap/slapd.conf -l /backup.ldif 50f98421 mdb_monitor_db_open: monitoring disabled; configure monitor database to enable -#################### 100.00% eta none elapsed 09m18s spd 4.6 M/s Closing DB...Error, entries missing! entry 1156449: cn=1356155776-83002,ou=... ,... ,ou=root (I shortened the entry DN in output with "...") I recognized this message before, but thought the entry was not imported ... > > We can prevent the SEGV but your database is still invalid because your LDIF > is invalid. Yes, will ask in the mailing list for additional information not directly releated to this SEGV. Thanks Kindly regards Maike

1 0

Re: (ITS#7499)
by hyc＠symas.com 24 Jan '13

24 Jan '13

Benin Technologies wrote: > Yes the fix worked (I downloaded the latest openldap.tar.gz on your > gitweb and installed it). Now slapd starts after having converted to > cn=config > > But after the conversion my ldapsearch returns an 80 error (with > slapd.conf it worked, the data from PostgreSQL where returned) > Thus my question : are there other steps to be taken after the > conversion (all I did was : slaptest -f slapd.conf -F slapd.d) Ah. In that case the fix must still be wrong. (Sorry, I'm patching this blind as I don't have any current SQL installation to test with.) > I don't think this has something to do with that 7499 bug, so I'll post > the question on the technical mailing list (but if nobody bumped into > that 7499 bug before, it logically means that nobody is using back-sql > with cn=config yet) Agreed, I think it's unlikely that anyone else has used this yet. > > ldapsearch -x -h localhost -b "dc=example,dc=com" "(objectClass=*)" > # extended LDIF > # > # LDAPv3 > # base <dc=example,dc=com> with scope subtree > # filter: (objectClass=*) > # requesting: ALL > # > > # search result > search: 2 > result: 80 Other (e.g., implementation specific) error > > # numResponses: 1 > > > Le 24/01/2013 04:46, Howard Chu a écrit : >> Benin Technologies wrote: >>>>>>> Yes, it's a bug. The conversion should have used double-quotes on >>> these >>>>>>> parameters. Will be fixed shortly. >>> >>> >>> ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in >>> the file olcDatabase={1}sql.ldif, like this : >>> >>> olcSqlInsEntryStmt: "insert into ldap_entries >>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>> ldap_entries),?,?,?,?)" >>> >>> >>> Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation >>> specific error)". With the old "slapd.conf", ldapsearch works fine. Is >>> there anything else to do when converting slapd.conf to cn=config on a >>> back-sql implementation ? >> >> Yes, actually the quotes are optional, but you must get the fix from git. >> Commit 56a0d9004f0fba943028041ea5af62338b6dfccd >>> >>> >>> >>> >>> Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >>>> benintechnologies(a)yahoo.fr wrote: >>>>> Hi, >>>>> >>>>> thank you for your reply >>>>> >>>>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>>>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>>>> >>>>> In that file, we have : >>>>> olcSqlInsEntryStmt: insert into ldap_entries >>>>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>>>> ldap_entries),?,?,?,?) >>>>> >>>>> it works with static configuration (slapd.conf) : I successfully >>>>> managed >>>>> to insert some data into the postgresql tables >>>>> >>>>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>>>> slapd.d) slapd doesn't start anymore : >>>>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>>>> <cn=root,dc=example,dc=com> >>>>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra >>>>> cruft >>>>> after<SQL expression>. >>>>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>>>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>>>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>>>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>>>> 50ff3f0a slapd destroy: freeing system resources. >>>>> 50ff3f0a slapd stopped. >>>>> 50ff3f0a connections_destroy: nothing to destroy. >>>>> >>>>> I believe it's a bug, no ? >>> >>> >> >> > > -- -- 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#7499)
by benintechnologies＠yahoo.fr 24 Jan '13

24 Jan '13

Yes the fix worked (I downloaded the latest openldap.tar.gz on your gitweb and installed it). Now slapd starts after having converted to cn=config But after the conversion my ldapsearch returns an 80 error (with slapd.conf it worked, the data from PostgreSQL where returned) Thus my question : are there other steps to be taken after the conversion (all I did was : slaptest -f slapd.conf -F slapd.d) I don't think this has something to do with that 7499 bug, so I'll post the question on the technical mailing list (but if nobody bumped into that 7499 bug before, it logically means that nobody is using back-sql with cn=config yet) ldapsearch -x -h localhost -b "dc=example,dc=com" "(objectClass=*)" # extended LDIF # # LDAPv3 # base <dc=example,dc=com> with scope subtree # filter: (objectClass=*) # requesting: ALL # # search result search: 2 result: 80 Other (e.g., implementation specific) error # numResponses: 1 Le 24/01/2013 04:46, Howard Chu a écrit : > Benin Technologies wrote: >> >>>>Yes, it's a bug. The conversion should have used double-quotes on >> these >> >>>>parameters. Will be fixed shortly. >> >> >> ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in >> the file olcDatabase={1}sql.ldif, like this : >> >> olcSqlInsEntryStmt: "insert into ldap_entries >> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >> ldap_entries),?,?,?,?)" >> >> >> Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation >> specific error)". With the old "slapd.conf", ldapsearch works fine. Is >> there anything else to do when converting slapd.conf to cn=config on a >> back-sql implementation ? > > Yes, actually the quotes are optional, but you must get the fix from git. > Commit 56a0d9004f0fba943028041ea5af62338b6dfccd >> >> >> >> >> Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >>> benintechnologies(a)yahoo.fr wrote: >>>> Hi, >>>> >>>> thank you for your reply >>>> >>>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>>> >>>> In that file, we have : >>>> olcSqlInsEntryStmt: insert into ldap_entries >>>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>>> ldap_entries),?,?,?,?) >>>> >>>> it works with static configuration (slapd.conf) : I successfully >>>> managed >>>> to insert some data into the postgresql tables >>>> >>>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>>> slapd.d) slapd doesn't start anymore : >>>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>>> <cn=root,dc=example,dc=com> >>>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra >>>> cruft >>>> after<SQL expression>. >>>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>>> 50ff3f0a slapd destroy: freeing system resources. >>>> 50ff3f0a slapd stopped. >>>> 50ff3f0a connections_destroy: nothing to destroy. >>>> >>>> I believe it's a bug, no ? >> >> > >

1 0

Re: (ITS#7498) Openldap syncrepl issue
by arunkumar_1123＠yahoo.com 23 Jan '13

23 Jan '13

> MMR has supported delta-syncrepl since 2.4.27. You should use it. I did consider delta-syncrepl, but given the high write load expected, I was not sure if it was the right decision. I am expecting an average load of 50-100 writes per second, and with 1 backup provider, and 10 consumers, it might get heavy on the provider which is serving the writes, given that OpenLDAP would be maintaining another DB for the access log. But with this syncrepl issue, it looks like I need to change the replication mode to refreshAndPersist anyway. As such it looks like delta syncrepl is also refreshAndPersist too. Is there any recommendation between simple refreshAndPersist and delta-syncrepl with refreshAndPersist for high write loads? Thanks PS: I see that delta syncrepl is compatible with MMR which I presume to be MultiMaster. I hope it works with Mirror Mode too. I did not find any documents supporting this.

1 0

(ITS#7501) added TCP keepalive support to back_ldap
by tedcheng＠symas.com 23 Jan '13

23 Jan '13

Full_Name: Ted C. Cheng Version: master OS: Linux/Solaris URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch Submission from: (NULL) (76.174.253.197) Please find in the URL a patch that adds TCP keepalive support to back_ldap. Please review and apply the patch. Thanks, Ted C. Cheng Symas Corporation

1 0

Re: (ITS#7499)
by hyc＠symas.com 23 Jan '13

23 Jan '13

Benin Technologies wrote: > >>>>Yes, it's a bug. The conversion should have used double-quotes on these > >>>>parameters. Will be fixed shortly. > > > ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in > the file olcDatabase={1}sql.ldif, like this : > > olcSqlInsEntryStmt: "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" > > > Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation > specific error)". With the old "slapd.conf", ldapsearch works fine. Is > there anything else to do when converting slapd.conf to cn=config on a > back-sql implementation ? Yes, actually the quotes are optional, but you must get the fix from git. Commit 56a0d9004f0fba943028041ea5af62338b6dfccd > > > > > Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >> benintechnologies(a)yahoo.fr wrote: >>> Hi, >>> >>> thank you for your reply >>> >>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>> >>> In that file, we have : >>> olcSqlInsEntryStmt: insert into ldap_entries >>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>> ldap_entries),?,?,?,?) >>> >>> it works with static configuration (slapd.conf) : I successfully managed >>> to insert some data into the postgresql tables >>> >>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>> slapd.d) slapd doesn't start anymore : >>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>> <cn=root,dc=example,dc=com> >>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft >>> after<SQL expression>. >>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>> 50ff3f0a slapd destroy: freeing system resources. >>> 50ff3f0a slapd stopped. >>> 50ff3f0a connections_destroy: nothing to destroy. >>> >>> I believe it's a bug, no ? > > -- -- 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#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

>>>>Yes, it's a bug. The conversion should have used double-quotes on these >>>>parameters. Will be fixed shortly. ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in the file olcDatabase={1}sql.ldif, like this : olcSqlInsEntryStmt: "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation specific error)". With the old "slapd.conf", ldapsearch works fine. Is there anything else to do when converting slapd.conf to cn=config on a back-sql implementation ? Le 24/01/2013 02:44, hyc(a)symas.com a écrit : > benintechnologies(a)yahoo.fr wrote: >> Hi, >> >> thank you for your reply >> >> I simply took the slapd.conf file adapted to PostgreSQL in the source >> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >> >> In that file, we have : >> olcSqlInsEntryStmt: insert into ldap_entries >> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >> ldap_entries),?,?,?,?) >> >> it works with static configuration (slapd.conf) : I successfully managed >> to insert some data into the postgresql tables >> >> But after having converted it to cn=config (slaptest -f slapd.conf -F >> slapd.d) slapd doesn't start anymore : >> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >> <cn=root,dc=example,dc=com> >> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft >> after<SQL expression>. >> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >> 50ff3f0a send_ldap_result: err=19 matched="" text="" >> 50ff3f0a slapd destroy: freeing system resources. >> 50ff3f0a slapd stopped. >> 50ff3f0a connections_destroy: nothing to destroy. >> >> I believe it's a bug, no ?

1 0

(ITS#7500) libldap starttls crashes if invalid GnuTLS cipher suite string
by jouko.orava＠iki.fi 23 Jan '13

23 Jan '13

Full_Name: Jouko Orava Version: 2.4.28, 2.4.33 OS: Debian/Ubuntu URL: Submission from: (NULL) (82.181.197.37) If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes in ldap_start_tls_s() due to a double free. See https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353 for my original bug submission, including a suggested patch, https://launchpadlibrarian.net/129174364/openldap-ciphersuite.patch and a simple example ldapsearch-like program that can be used to test the issue. This bug is not critical, since using a valid GnuTLS cipher suite does work, for example "NORMAL" or "SECURE256". However, trying to use anything more specific is exceedingly difficult -- basically trial and error, due to applications crashing in libldap with an invalid one. The two other TLS implementations in OpenLDAP are not affected by this bug. The double free occurs in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo->ldo_tls_ctx); call in the error_exit: path. Because the cipher suite string was unacceptable to GnuTLS, the context is either released by GnuTLS or never properly initialized. The error_exit: path tries to release that context, and causes the C library to abort the program as it detects a double free. Simply commenting the ldap_pvt_tls_ctx_free(lo->ldo_tls_ctx); call in the error_exit: path in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx() masks the issue, but is obviously incorrect (as it affects the two other TLS implementations too). My suggested patch is to use the configured cipher suite string when creating the new TLS context, instead of "NORMAL" as is currently done, in openldap/libraries/libldap/tls_g.c:tlsg_ctx_new(). If there is a problem with the cipher suite priority string, the initial context is torn down, and caught earlier in openldap/libraries/libldap/tls2.c, avoiding the crash. (However, the cipher suite string will be parsed twice.) There seem to be numerous unhandled bug reports in various distributions and applications, including http://www.openldap.org/its/index.cgi/Incoming?id=6939#themesg which are quite tricky to investigate, as the actual bug occurs deep in libldap. Only user checks with a patched libldap will prove whether these are actually caused by this bug or not. It is very easy to assume it is an application bug, due to the symptoms and pretty limited circumstances. Recap: libldap + GnuTLS, application using ldap_start_tls, and any cipher suite string not acceptable to GnuTLS will cause libldap to crash due to a double free.

1 0

Re: (ITS#7499)
by hyc＠symas.com 23 Jan '13

23 Jan '13

benintechnologies(a)yahoo.fr wrote: > Hi, > > thank you for your reply > > I simply took the slapd.conf file adapted to PostgreSQL in the source > (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) > > In that file, we have : > olcSqlInsEntryStmt: insert into ldap_entries > (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from > ldap_entries),?,?,?,?) > > it works with static configuration (slapd.conf) : I successfully managed > to insert some data into the postgresql tables > > But after having converted it to cn=config (slaptest -f slapd.conf -F > slapd.d) slapd doesn't start anymore : > 0ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, > <cn=root,dc=example,dc=com> > 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft > after <SQL expression>. > 50ff3f0a config error processing olcDatabase={1}sql,cn=config: > <olcSqlInsEntryStmt> *extra cruft after <SQL expression>* > 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 > 50ff3f0a send_ldap_result: err=19 matched="" text="" > 50ff3f0a slapd destroy: freeing system resources. > 50ff3f0a slapd stopped. > 50ff3f0a connections_destroy: nothing to destroy. > > I believe it's a bug, no ? Yes, it's a bug. The conversion should have used double-quotes on these parameters. Will be fixed shortly. -- -- 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#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

Hi, thank you for your reply I simply took the slapd.conf file adapted to PostgreSQL in the source (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) In that file, we have : olcSqlInsEntryStmt: insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?) it works with static configuration (slapd.conf) : I successfully managed to insert some data into the postgresql tables But after having converted it to cn=config (slaptest -f slapd.conf -F slapd.d) slapd doesn't start anymore : 0ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, <cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft after <SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> *extra cruft after <SQL expression>* 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. I believe it's a bug, no ? thanks BT Le 24/01/2013 00:39, quanah(a)zimbra.com a écrit : > --On Wednesday, January 23, 2013 10:58 PM +0000 benintechnologies(a)yahoo.fr > wrote: > >> I just noticed I forgot some infos, so here is the problem again : >> >> If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the >> line starting with olcSqlInsEntryStmt, then slapd starts fine. >> >> So what's the right syntax for olcSqlInsEntryStmt ??? > > From the man page: > > > insentry_stmt<SQL expression> > The statement that is used to insert a new entry in table > ldap_entries; see "METAINFORMATION USED" for details. The > default is "INSERT INTO ldap_entries (dn, oc_map_id, parent, > keyval) VALUES (?, ?, ?, ?)". > > --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#7499)
by quanah＠zimbra.com 23 Jan '13

23 Jan '13

--On Wednesday, January 23, 2013 10:58 PM +0000 benintechnologies(a)yahoo.fr wrote: > I just noticed I forgot some infos, so here is the problem again : > > If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the > line starting with olcSqlInsEntryStmt, then slapd starts fine. > > So what's the right syntax for olcSqlInsEntryStmt ??? >From the man page: insentry_stmt <SQL expression> The statement that is used to insert a new entry in table ldap_entries; see "METAINFORMATION USED" for details. The default is "INSERT INTO ldap_entries (dn, oc_map_id, parent, keyval) VALUES (?, ?, ?, ?)". --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

(ITS#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

I just noticed I forgot some infos, so here is the problem again : Hi, Has anyone out there managed to successfully convert slapd.conf into cn=config with back-sql enabled ? I'm on Debian 6 / OpenLDAP 2.4.33 with back-sql support (./configure --enable-sql) According tohttp://www.openldap.org/software/release/changes.html, back-sql supports dynamic config as of version 2.4.27. So I converted slapd.conf to slapd.d, conversion went well. However, when I start slapd, I get the following message : # /usr/local/libexec/slapd -u openldap -g openldap -d -1 ....... 50ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>,<cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft after<SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> extra cruft after<SQL expression> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. The error message seems to be "extra cruft after<SQL expression>" If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the line starting with olcSqlInsEntryStmt, then slapd starts fine. So what's the right syntax for olcSqlInsEntryStmt ??? Thanks Ben

1 0

(ITS#7499) bug on dynamic configuration with back-sql
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

Full_Name: Ben Tech Version: 2.4.33 OS: Debian 6.0.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (41.85.161.126) Hi, I'm on Debian 6 / OpenLDAP 2.4.33 with back-sql. According to http://www.openldap.org/software/release/changes.html, back-sql supports dynamic config as of version 2.4.27. So I converted slapd.conf to slapd.d, conversion went well. However, when I start slapd, I get the following message : # /usr/local/libexec/slapd -u openldap -g openldap -d -1 ....... 50ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, <cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft after <SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> extra cruft after <SQL expression> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. If I comment that line, the server starts fine # olcSqlInsEntryStmt: insert into ldap_entries (id,dn,oc_map_id,parent,keyval) v alues ((select max(id)+1 from ldap_entries),?,?,?,?)

1 0

Re: (ITS#7495) access filter not correctly validated if assertion attribute not requested
by michael＠stroeder.com 23 Jan '13

23 Jan '13

Using extra_attrs would be a possible work-around (tested). Unfortunately it seems to trigger a seg fault in slapo-rwm in my setup which is hard to track down to a certain cause. slapd starts ok but quite soon a seg fault message is written to syslog. Just before the seg fault I see the usual search requests of sssd in the logs... Ciao, Michael.

1 0

Re: (ITS#7498) Openldap syncrepl issue
by quanah＠zimbra.com 23 Jan '13

23 Jan '13

--On Wednesday, January 23, 2013 11:59 AM +0000 arunkumar_1123(a)yahoo.com wrote: > Full_Name: Arunkumar shanmugam > Version: 2.4.33 > OS: rhel5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (203.83.248.32) > > > Hi, > > I've been having issues with syncrepl in openldap. This is plain > syncrepl. I'm not using delta-syncrepl as I run with mirror mode on. MMR has supported delta-syncrepl since 2.4.27. You should use it. --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

(ITS#7498) Openldap syncrepl issue
by arunkumar_1123＠yahoo.com 23 Jan '13

23 Jan '13

Full_Name: Arunkumar shanmugam Version: 2.4.33 OS: rhel5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (203.83.248.32) Hi, I've been having issues with syncrepl in openldap. This is plain syncrepl. I'm not using delta-syncrepl as I run with mirror mode on. I've noticed that when there are a large number of writes on the writemaster (Typically around 10 per second) the data on the readslave goes out of sync with the master, typically having entries which have been deleted on the master. The contextCSNs on both the readslaves and writemaster match eventually, but the data doesn't. I'm running the readslave in refreshOnly mode with an interval of 1 minute. I'm using a reasonably large DB of size ~ 2 GB. I turned on the sync logs and found lots of entries with "nonpresent_callback" and "syncrepl_del_nonpresent". Tested this and found it occurring in both 2.4.29 and 2.4.33 (Latest as of this time), and with BDB 4.2.36 as the backend. I was wondering if anyone has faced similar issues before, and if there exists a solution to this problem. I will send any relevant configuration and log snippets as needed. Thanks

1 0

(ITS#7497) ldif_read_record line number overflow
by hyc＠OpenLDAP.org 22 Jan '13

22 Jan '13

Full_Name: Howard Chu Version: RE24/master OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (78.155.233.73) Submitted by: hyc While trying to load a 150 million entry LDIF file using slapadd, it would finish with no errors but only ~107 million entries were loaded. This turns out to be because at 20 lines per record, the LDIF file contained 3 billion lines, and the line number counter is a signed int. And in slapadd, we have the "jumpline" option to skip some number of input lines, when resuming an interrupted load. The jumpline defaults to 0, if the input line number is less than the jumpline the record is silently skipped. After reading the 2147483647th line of the file, it discards all of the rest until hitting EOF. Will fix this by changing the parameter to unsigned long. This is unfortunately going to require a libldap version bump.

1 0

Re: (ITS#7475) documenting that dynamic lists/groups overlays are mutually exclusive with the memberof overlay
by tedcheng＠symas.com 22 Jan '13

22 Jan '13

On Jan 22, 2013, at 4:40 AM, Howard Chu wrote: > tedcheng(a)symas.com wrote: >> Full_Name: Ted C. Cheng >> Version: trunk >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (76.174.253.197) >> >> >> Document enhancement request: >> >> Dynamic lists/groups do not involve group entry modification. As a result, they >> cannot be used with the memberof overlay. Would the above text, in one single paragraph, be good enough for the documentation? >> >> It would be great to document explicitly, man pages and admin guide, that >> dynamic lists/groups overlays and memberof overlay are mutually exclusive. > > If you have suggested text, please submit the patch here. > Ted C. Cheng Symas Corporation

1 0

Re: (ITS#7475) documenting that dynamic lists/groups overlays are mutually exclusive with the memberof overlay
by hyc＠symas.com 22 Jan '13

22 Jan '13

tedcheng(a)symas.com wrote: > Full_Name: Ted C. Cheng > Version: trunk > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (76.174.253.197) > > > Document enhancement request: > > Dynamic lists/groups do not involve group entry modification. As a result, they > cannot be used with the memberof overlay. > > It would be great to document explicitly, man pages and admin guide, that > dynamic lists/groups overlays and memberof overlay are mutually exclusive. If you have suggested text, please submit the patch here. -- -- 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#7496) Segemtation fault in mdb_entry_decode
by hyc＠symas.com 22 Jan '13

22 Jan '13

meike.stone(a)googlemail.com wrote: > Full_Name: Meike Stone > Version: 2.4.33 and git > OS: Linux / SLES11 SP2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (193.200.138.3) > > > I use a Database with about 1,500,000 entires and 2,5GByte ldif from slapcat. > This database was exported from our production system running bdb-backend. > > The Problem exist in Version 2.4.33, therefore I took the slapd source from git > (2013/01/21) and I compiled slapd with debugging symbols. > Thread 1 (Thread 0x7f738b21c700 (LWP 19394)): > #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at > search.c:720 > scopeok = 1 > edata = {mv_size = 0, mv_data = 0x7f74bbb99728} This indicates that the entry being debugged is actually zero bytes, i.e. it's not a valid entry at all. Nodes like this get stored in the database during slapadd when a child entry gets added before its parent; a zero-byte stub is stored as a placeholder for the missing parent. When you ran slapadd you should have seen warning messages about missing entries, telling you that your LDIF is incomplete. We can prevent the SEGV but your database is still invalid because your LDIF is invalid. > mdb = 0x7f760eff4010 > id = 1156449 > cursor = 1156449 > lastid = 18446744073709551615 -- -- 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#7496) Segemtation fault in mdb_entry_decode
by meike.stone＠googlemail.com 22 Jan '13

22 Jan '13

Full_Name: Meike Stone Version: 2.4.33 and git OS: Linux / SLES11 SP2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.200.138.3) I use a Database with about 1,500,000 entires and 2,5GByte ldif from slapcat. This database was exported from our production system running bdb-backend. The Problem exist in Version 2.4.33, therefore I took the slapd source from git (2013/01/21) and I compiled slapd with debugging symbols. My test configuration is simple: -------------------------------------------- include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/yast.schema include /etc/openldap/schema/rfc2307bis.schema include /etc/openldap/schema/my_ldap_attributes.schema include /etc/openldap/schema/my_ldap_ObjectClasses.schema pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args sizelimit -1 timelimit 300 disallow bind_anon require authc gentlehup on tool-threads 4 serverID 001 ############################ # mdb database definitions ############################ database mdb suffix "ou=root" rootdn "cn=admin,ou=root" rootpw password directory /var/lib/ldap/ldap.mdb loglevel 256 maxsize 10737418240 envflags writemap,nometasync index objectClass,entryUUID,entryCSN eq index cn eq,sub . . . some other own indexes here -------------------------------------------- I started my search via: /tmp/ol/usr/local/bin/ldapsearch -x -h localhost -w password -D cn=admin,ou=root -b'ou=root' '(objectClass=*)' >/dev/null and got in the syslog following meassge: Jan 21 17:50:31 debld02 kernel: [348860.053152] slapd[19394]: segfault at 7f760f974ce8 ip 000000000053bea1 sp 00007f738b10a650 error 4 in slapd [400000+227000] Because of this, I configured the kernel to core dump: sysctl -w kernel.core_pattern=/tmp/core sysctl -w kernel.core_uses_pid=1 sysctl -w kernel.suid_dumpable=2 ulimit -c unlimited ulimit -v unlimited Here is the output from Backtrace: (gdb) bt #0 0x000000000053bea1 in mdb_entry_decode (op=0xc3a020, data=0x7f738b10a770, e=0x7f738b11a828) at id2entry.c:666 #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:720 #2 0x0000000000433d41 in fe_op_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:402 #3 0x0000000000433647 in do_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:247 #4 0x00000000004300f5 in connection_operation (ctx=0x7f738b21bb80, arg_v=0xc3a020) at connection.c:1150 #5 0x0000000000430694 in connection_read_thread (ctx=0x7f738b21bb80, argv=0x9) at connection.c:1286 #6 0x0000000000566c0b in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:688 #7 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 #8 0x00007f760db31c5d in clone () from /lib64/libc.so.6 #9 0x0000000000000000 in ?? () ======================================== (gdb) bt full #0 0x000000000053bea1 in mdb_entry_decode (op=0xc3a020, data=0x7f738b10a770, e=0x7f738b11a828) at id2entry.c:666 have_nval = 0 mdb = 0x7f760eff4010 i = 0 j = 0 nattrs = 2600 nvals = 524289 rc = 32627 a = 0x7f73886fa060 x = 0x7f73886fa010 text = 0x1 <Address 0x1 out of bounds> ad = 0x11a561 lp = 0x7f74bbb99738 ptr = 0x7f74bbb99738 <Address 0x7f74bbb99738 out of bounds> bptr = 0x7f73887187e0 #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:720 scopeok = 1 edata = {mv_size = 0, mv_data = 0x7f74bbb99728} mdb = 0x7f760eff4010 id = 1156449 cursor = 1156449 lastid = 18446744073709551615 candidates = {18446744073709551615, 1, 18446744073709551615, 0 <repeats 130260 times>, 140145012714441, 0, 140145012852253, 8589940736, 0, 1102570112642121728, 140134232198960, 0, 0, 4294969344, 0, 144115737831604224, 140134232199008, 0, 0, 4294969344, 0, 72058143793676288, 0, 0, 140145012852253, 562962838323220, 83263594790786, 4294967296, 72058139498840072, 72058139498905608, 18446743519659032584, 122509647347719, 563035852767288, 83263594790786, 8564836354, 144115733536768008, 144115733536833544, 18446743519659032584, 122509647347719, 563035852767292, 83263594790786, 8598329346, 1102570108347285512, 1102570108347351048, 18396392677450186760, 3488165888539164681, 0 <repeats 252 times>, 140145015511498, 24, 140134232201360, 140134232201280, 0, 0, 0, 2050, 0, 0, 0, 0, 140134232201392, 140134240594784, 5912807, 0, 38654705665, 0, 8804682956800, 140134232205552, 5910925, 4294967296, 140144980134384, 17179869184, 10555744, 0 <repeats 35 times>, 4764301, 0, 0, 9576736, 140134232205088, 0, 140134232205088, 9576736, 0, 140134232201856, 5642426, 9576736, 4764202, 140134232205088, 9576768, 0, 0, 140134232201920, 4764448, 0, 9576416, 9576416, 140134232205088, 0, 9576736, 140134232205248, 4752534, 0, 4764301, 140134232205360, 12821496, 9317456, 140134232205312, 0, 140134232205312, 9317456, 0, 140134232202080, 5642426, 9317456, 4764202, 140134232205312, 9317488, 0, 0, 140134232202144, 4764448, 0, 9317136, 9317136, 140134232205312, 0, 9317456, 140134232205472, 4752534, 0, 140134232210000, 140134232205576, 140134232205552, 0 <repeats 42 times>, 3, 140134232204592, 140134232204608, 12, 3, 140145012098155, 18446730733541130240, 140134232204444, 140134232204432, 140134232204488, 0, 0, 140134232204336, 140134232213248, 0, 0, 0, 0, 0, 140134232203296, 0, 0, 0, 0, 5956991, 5956996, 0, 18446744073709551615, 140134232202872, 64, 140145015434880...} scopes = 0x7f7389f1a010 e = 0x0 base = 0xc3a548 matched = 0x0 attrs = 0x0 mask = 5119 stoptime = 1358790564 manageDSAit = 0 tentries = -1 isc = {mt = 0xd3bd50, mc = 0xd3d840, id = 1156449, scopes = 0x7f7389f1a010, numrdns = 7, nscope = 1, rdns = {{bv_len = 19, bv_val = 0x7f74bbba594e <Address 0x7f74bbba594e out of bounds>}, {bv_len = 19, bv_val = 0x7f74bbba29b8 <Address 0x7f74bbba29b8 out of bounds>}, {bv_len = 9, bv_val = 0x7f738e1bffee <Address 0x7f738e1bffee out of bounds>}, {bv_len = 19, bv_val = 0x7f74ad2f49b4 <Address 0x7f74ad2f49b4 out of bounds>}, {bv_len = 18, bv_val = 0x7f74ad2f4821 <Address 0x7f74ad2f4821 out of bounds>}, {bv_len = 19, bv_val = 0x7f74a7f47696 <Address 0x7f74a7f47696 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 0, bv_val = 0x0} <repeats 2039 times>}, nrdns = {{bv_len = 19, bv_val = 0x7f74bbba593a <Address 0x7f74bbba593a out of bounds>}, {bv_len = 19, bv_val = 0x7f74bbba29a4 <Address 0x7f74bbba29a4 out of bounds>}, {bv_len = 9, bv_val = 0x7f738e1bffe4 <Address 0x7f738e1bffe4 out of bounds>}, {bv_len = 19, bv_val = 0x7f74ad2f49a0 <Address 0x7f74ad2f49a0 out of bounds>}, {bv_len = 18, bv_val = 0x7f74ad2f480e <Address 0x7f74ad2f480e out of bounds>}, {bv_len = 19, bv_val = 0x7f74a7f47682 <Address 0x7f74a7f47682 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 0, bv_val = 0x0} <repeats 2039 times>}} mci = 0xd3d6b0 opinfo = {moi_oe = {oe_next = {sle_next = 0x0}, oe_key = 0x7f760eff4010}, moi_txn = 0xd3bd50, moi_ref = 1, moi_flag = 1 '\001'} moi = 0x7f738b10a7c0 ltid = 0xd3bd50 #2 0x0000000000433d41 in fe_op_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:402 bd = 0x836180 #3 0x0000000000433647 in do_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:247 base = {bv_len = 7, bv_val = 0xc39f97 "ou=root"} siz = 0 off = 0 i = 0 #4 0x00000000004300f5 in connection_operation (ctx=0x7f738b21bb80, arg_v=0xc3a020) at connection.c:1150 rc = 80 cancel = 0 op = 0xc3a020 rs = {sr_type = REP_SEARCH, sr_tag = 0, sr_msgid = 0, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = { sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 1156423, r_v2ref = 0x0}, sru_sasl = { r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 99 opidx = SLAP_OP_SEARCH conn = 0x7f760bc209f0 memctx = 0xa11320 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #5 0x0000000000430694 in connection_read_thread (ctx=0x7f738b21bb80, argv=0x9) at connection.c:1286 rc = 0 cri = {op = 0xc3a020, func = 0, arg = 0x0, ctx = 0x7f738b21bb80, nullop = 0} s = 9 #6 0x0000000000566c0b in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:688 pool = 0x8ef460 task = 0xa11490 work_list = 0x8ef4f8 ctx = {ltu_id = 140134232213248, ltu_key = {{ltk_key = 0x42fbef, ltk_data = 0xc39d50, ltk_free = 0x42fa3b <conn_counter_destroy>}, { ltk_key = 0x4a2675, ltk_data = 0xa11320, ltk_free = 0x4a24a4 <slap_sl_mem_destroy>}, {ltk_key = 0x44aba4, ltk_data = 0x0, ltk_free = 0x44aafc <slap_op_q_destroy>}, {ltk_key = 0x7f760ba1e010, ltk_data = 0xd3bd50, ltk_free = 0x53b0f7 <mdb_reader_free>}, { ltk_key = 0x502c94, ltk_data = 0x7f7388f19010, ltk_free = 0x502c74 <search_stack_free>}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 27 times>}} kctx = 0x0 i = 32 keyslot = 805 hash = 2547932965 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #7 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #8 0x00007f760db31c5d in clone () from /lib64/libc.so.6 No symbol table info available. #9 0x0000000000000000 in ?? () No symbol table info available. ======================================== (gdb) thread apply all bt Thread 4 (Thread 0x7f760f155700 (LWP 19386)): #0 0x00007f760ddd6f95 in pthread_join () from /lib64/libpthread.so.0 #1 0x000000000056814b in ldap_pvt_thread_join (thread=140134240605952, thread_return=0x0) at thr_posix.c:197 #2 0x000000000042d01e in slapd_daemon () at daemon.c:2935 #3 0x0000000000409029 in main (argc=11, argv=0x7fffd76de248) at main.c:1013 Thread 3 (Thread 0x7f738ba1d700 (LWP 19387)): #0 0x00007f760db322e3 in epoll_wait () from /lib64/libc.so.6 #1 0x000000000042be25 in slapd_daemon_task (ptr=0xa10ec0) at daemon.c:2542 #2 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 #3 0x00007f760db31c5d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f738aa1b700 (LWP 19395)): #0 0x00007f760ddda61c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00000000005681f3 in ldap_pvt_thread_cond_wait (cond=0x8ef490, mutex=0x8ef468) at thr_posix.c:277 #2 0x0000000000566b6c in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:675 #3 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f760db31c5d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f738b21c700 (LWP 19394)): #0 0x000000000053bea1 in mdb_entry_decode (op=0xc3a020, data=0x7f738b10a770, e=0x7f738b11a828) at id2entry.c:666 #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:720 #2 0x0000000000433d41 in fe_op_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:402 #3 0x0000000000433647 in do_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:247 #4 0x00000000004300f5 in connection_operation (ctx=0x7f738b21bb80, arg_v=0xc3a020) at connection.c:1150 #5 0x0000000000430694 in connection_read_thread (ctx=0x7f738b21bb80, argv=0x9) at connection.c:1286 #6 0x0000000000566c0b in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:688 #7 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 #8 0x00007f760db31c5d in clone () from /lib64/libc.so.6 #9 0x0000000000000000 in ?? () ======================================== (gdb) thread apply all bt full Thread 4 (Thread 0x7f760f155700 (LWP 19386)): #0 0x00007f760ddd6f95 in pthread_join () from /lib64/libpthread.so.0 No symbol table info available. #1 0x000000000056814b in ldap_pvt_thread_join (thread=140134240605952, thread_return=0x0) at thr_posix.c:197 No locals. #2 0x000000000042d01e in slapd_daemon () at daemon.c:2935 i = 0 rc = 0 #3 0x0000000000409029 in main (argc=11, argv=0x7fffd76de248) at main.c:1013 i = 11 no_detach = 0 rc = -12 urls = 0x8bf090 "ldap:/// " username = 0x8bf0e0 "root" groupname = 0x8bf100 "ldap" sandbox = 0x0 syslogUser = 160 pid = 0 waitfds = {8, 9} g_argc = 11 g_argv = 0x7fffd76de248 configfile = 0x8bf0b0 "/etc/openldap/slapd.conf" configdir = 0x0 serverName = 0x7fffd76df6c0 "slapd" serverMode = 1 scp = 0x0 scp_entry = 0x0 debug_unknowns = 0x0 syslog_unknowns = 0x0 serverNamePrefix = 0x5a4ebd "" l = 4218987 slapd_pid_file_unlink = 1 slapd_args_file_unlink = 1 firstopt = 0 __PRETTY_FUNCTION__ = "main" Thread 3 (Thread 0x7f738ba1d700 (LWP 19387)): #0 0x00007f760db322e3 in epoll_wait () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000042be25 in slapd_daemon_task (ptr=0xa10ec0) at daemon.c:2542 ns = 1 at = 0 nfds = 3 revents = 0x8c4700 tvp = 0x0 cat = {tv_sec = 0, tv_usec = 0} i = 1 nwriters = 0 now = 1358790631 tv = {tv_sec = 0, tv_usec = 0} tdelta = 1 rtask = 0x0 l = 1 last_idle_check = 1358790529 ebadf = 0 tid = 0 #2 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #3 0x00007f760db31c5d in clone () from /lib64/libc.so.6 No symbol table info available. #4 0x0000000000000000 in ?? () No symbol table info available. Thread 2 (Thread 0x7f738aa1b700 (LWP 19395)): #0 0x00007f760ddda61c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 No symbol table info available. #1 0x00000000005681f3 in ldap_pvt_thread_cond_wait (cond=0x8ef490, mutex=0x8ef468) at thr_posix.c:277 No locals. #2 0x0000000000566b6c in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:675 pool = 0x8ef460 task = 0x0 work_list = 0x8ef4f8 ctx = {ltu_id = 140134223820544, ltu_key = {{ltk_key = 0x42fbef, ltk_data = 0xb39c30, ltk_free = 0x42fa3b <conn_counter_destroy>}, { ltk_key = 0x4a2675, ltk_data = 0xb397b0, ltk_free = 0x4a24a4 <slap_sl_mem_destroy>}, {ltk_key = 0x44aba4, ltk_data = 0xb39870, ltk_free = 0x44aafc <slap_op_q_destroy>}, {ltk_key = 0x7f760ba1e010, ltk_data = 0xd3a3f0, ltk_free = 0x53b0f7 <mdb_reader_free>}, { ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 28 times>}} kctx = 0x0 i = 32 keyslot = 660 hash = 2646102676 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #3 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #4 0x00007f760db31c5d in clone () from /lib64/libc.so.6 No symbol table info available. #5 0x0000000000000000 in ?? () No symbol table info available. Thread 1 (Thread 0x7f738b21c700 (LWP 19394)): #0 0x000000000053bea1 in mdb_entry_decode (op=0xc3a020, data=0x7f738b10a770, e=0x7f738b11a828) at id2entry.c:666 have_nval = 0 mdb = 0x7f760eff4010 i = 0 j = 0 nattrs = 2600 nvals = 524289 rc = 32627 a = 0x7f73886fa060 x = 0x7f73886fa010 ---Type <return> to continue, or q <return> to quit--- text = 0x1 <Address 0x1 out of bounds> ad = 0x11a561 lp = 0x7f74bbb99738 ptr = 0x7f74bbb99738 <Address 0x7f74bbb99738 out of bounds> bptr = 0x7f73887187e0 #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:720 scopeok = 1 edata = {mv_size = 0, mv_data = 0x7f74bbb99728} mdb = 0x7f760eff4010 id = 1156449 cursor = 1156449 lastid = 18446744073709551615 candidates = {18446744073709551615, 1, 18446744073709551615, 0 <repeats 130260 times>, 140145012714441, 0, 140145012852253, 8589940736, 0, 1102570112642121728, 140134232198960, 0, 0, 4294969344, 0, 144115737831604224, 140134232199008, 0, 0, 4294969344, 0, 72058143793676288, 0, 0, 140145012852253, 562962838323220, 83263594790786, 4294967296, 72058139498840072, 72058139498905608, 18446743519659032584, 122509647347719, 563035852767288, 83263594790786, 8564836354, 144115733536768008, 144115733536833544, 18446743519659032584, 122509647347719, 563035852767292, 83263594790786, 8598329346, 1102570108347285512, 1102570108347351048, 18396392677450186760, 3488165888539164681, 0 <repeats 252 times>, 140145015511498, 24, 140134232201360, 140134232201280, 0, 0, 0, 2050, 0, 0, 0, 0, 140134232201392, 140134240594784, 5912807, 0, 38654705665, 0, 8804682956800, 140134232205552, 5910925, 4294967296, 140144980134384, 17179869184, 10555744, 0 <repeats 35 times>, 4764301, 0, 0, 9576736, 140134232205088, 0, 140134232205088, 9576736, 0, 140134232201856, 5642426, 9576736, 4764202, 140134232205088, 9576768, 0, 0, 140134232201920, 4764448, 0, 9576416, 9576416, 140134232205088, 0, 9576736, 140134232205248, 4752534, 0, 4764301, 140134232205360, 12821496, 9317456, 140134232205312, 0, 140134232205312, 9317456, 0, 140134232202080, 5642426, 9317456, 4764202, 140134232205312, 9317488, 0, 0, 140134232202144, 4764448, 0, 9317136, 9317136, 140134232205312, 0, 9317456, 140134232205472, 4752534, 0, 140134232210000, 140134232205576, 140134232205552, 0 <repeats 42 times>, 3, 140134232204592, 140134232204608, 12, 3, 140145012098155, 18446730733541130240, 140134232204444, 140134232204432, 140134232204488, 0, 0, 140134232204336, 140134232213248, 0, 0, 0, 0, 0, 140134232203296, 0, 0, 0, 0, 5956991, 5956996, 0, 18446744073709551615, 140134232202872, 64, 140145015434880...} scopes = 0x7f7389f1a010 e = 0x0 base = 0xc3a548 matched = 0x0 attrs = 0x0 mask = 5119 stoptime = 1358790564 manageDSAit = 0 tentries = -1 isc = {mt = 0xd3bd50, mc = 0xd3d840, id = 1156449, scopes = 0x7f7389f1a010, numrdns = 7, nscope = 1, rdns = {{bv_len = 19, bv_val = 0x7f74bbba594e <Address 0x7f74bbba594e out of bounds>}, {bv_len = 19, bv_val = 0x7f74bbba29b8 <Address 0x7f74bbba29b8 out of bounds>}, {bv_len = 9, bv_val = 0x7f738e1bffee <Address 0x7f738e1bffee out of bounds>}, {bv_len = 19, bv_val = 0x7f74ad2f49b4 <Address 0x7f74ad2f49b4 out of bounds>}, {bv_len = 18, bv_val = 0x7f74ad2f4821 <Address 0x7f74ad2f4821 out of bounds>}, {bv_len = 19, bv_val = 0x7f74a7f47696 <Address 0x7f74a7f47696 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bbd <Address 0x7f74bc3d2bbd out of bounds>}, {bv_len = 0, bv_val = 0x0} <repeats 2039 times>}, nrdns = {{bv_len = 19, bv_val = 0x7f74bbba593a <Address 0x7f74bbba593a out of bounds>}, {bv_len = 19, bv_val = 0x7f74bbba29a4 <Address 0x7f74bbba29a4 out of bounds>}, {bv_len = 9, bv_val = 0x7f738e1bffe4 <Address 0x7f738e1bffe4 out of bounds>}, {bv_len = 19, bv_val = 0x7f74ad2f49a0 <Address 0x7f74ad2f49a0 out of bounds>}, {bv_len = 18, bv_val = 0x7f74ad2f480e <Address 0x7f74ad2f480e out of bounds>}, {bv_len = 19, bv_val = 0x7f74a7f47682 <Address 0x7f74a7f47682 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 12, bv_val = 0x7f74bc3d2bb0 <Address 0x7f74bc3d2bb0 out of bounds>}, {bv_len = 0, bv_val = 0x0} <repeats 2039 times>}} mci = 0xd3d6b0 opinfo = {moi_oe = {oe_next = {sle_next = 0x0}, oe_key = 0x7f760eff4010}, moi_txn = 0xd3bd50, moi_ref = 1, moi_flag = 1 '\001'} moi = 0x7f738b10a7c0 ltid = 0xd3bd50 #2 0x0000000000433d41 in fe_op_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:402 bd = 0x836180 #3 0x0000000000433647 in do_search (op=0xc3a020, rs=0x7f738b21ba30) at search.c:247 base = {bv_len = 7, bv_val = 0xc39f97 "ou=root"} siz = 0 off = 0 i = 0 #4 0x00000000004300f5 in connection_operation (ctx=0x7f738b21bb80, arg_v=0xc3a020) at connection.c:1150 rc = 80 cancel = 0 op = 0xc3a020 rs = {sr_type = REP_SEARCH, sr_tag = 0, sr_msgid = 0, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = { sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 1156423, r_v2ref = 0x0}, sru_sasl = { r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 99 opidx = SLAP_OP_SEARCH conn = 0x7f760bc209f0 memctx = 0xa11320 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #5 0x0000000000430694 in connection_read_thread (ctx=0x7f738b21bb80, argv=0x9) at connection.c:1286 rc = 0 cri = {op = 0xc3a020, func = 0, arg = 0x0, ctx = 0x7f738b21bb80, nullop = 0} s = 9 #6 0x0000000000566c0b in ldap_int_thread_pool_wrapper (xpool=0x8ef460) at tpool.c:688 pool = 0x8ef460 task = 0xa11490 work_list = 0x8ef4f8 ctx = {ltu_id = 140134232213248, ltu_key = {{ltk_key = 0x42fbef, ltk_data = 0xc39d50, ltk_free = 0x42fa3b <conn_counter_destroy>}, { ltk_key = 0x4a2675, ltk_data = 0xa11320, ltk_free = 0x4a24a4 <slap_sl_mem_destroy>}, {ltk_key = 0x44aba4, ltk_data = 0x0, ltk_free = 0x44aafc <slap_op_q_destroy>}, {ltk_key = 0x7f760ba1e010, ltk_data = 0xd3bd50, ltk_free = 0x53b0f7 <mdb_reader_free>}, { ltk_key = 0x502c94, ltk_data = 0x7f7388f19010, ltk_free = 0x502c74 <search_stack_free>}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 27 times>}} kctx = 0x0 i = 32 keyslot = 805 hash = 2547932965 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #7 0x00007f760ddd67b6 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. #8 0x00007f760db31c5d in clone () from /lib64/libc.so.6 No symbol table info available. #9 0x0000000000000000 in ?? () No symbol table info available.

1 0

Re: (ITS#7495) access filter not correctly validated if assertion attribute not requested
by michael＠stroeder.com 18 Jan '13

18 Jan '13

This is a cryptographically signed message in MIME format. --------------ms090800020408080308010509 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hallvard B Furuseth wrote: > Cannot reproduce on RedHat Linux, x86_64. But then, the info was > rather brief. (E.g. which backend? Was that a per-backend or global > ACL? Might some overlays or other access statements interefere?) >=20 > Anyway, please provide a complete config and preferably LDIF which > demonstrates the problem. Thanks for looking it this. As usual this is a more complex customer setup with many ACLs and several= overlays. I tried to provide a simple example but I also see that this do= es not show the issue on my local machine. I will try to strip down the complex config. But this will take a while. Ciao, Michael. --------------ms090800020408080308010509 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCC BT8wggQnoAMCAQICDwCmSwABAAIAivjZQ8SBvzANBgkqhkiG9w0BAQUFADB8MQswCQYDVQQG EwJERTEcMBoGA1UEChMTVEMgVHJ1c3RDZW50ZXIgR21iSDElMCMGA1UECxMcVEMgVHJ1c3RD ZW50ZXIgQ2xhc3MgMSBMMSBDQTEoMCYGA1UEAxMfVEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBM MSBDQSBJWDAeFw0xMjA2MDYxOTAyMTZaFw0xMzA2MDcxOTAyMTZaMCgxCzAJBgNVBAYTAkRF MRkwFwYDVQQDDBBNaWNoYWVsIFN0csO2ZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAxXZGav40rnGNLxEggBW94MILWHlfC8a23Jew5U1gPlfRTXOjjzmoaZ1uCyGdgF6M VvuO9T1aTQNGH+OdeGe3P7Tfc/NsLJFJ2wtd8blvhmodUgse2eypiWjNOd4gZuhalBhgsQ0K b5D6/1foghII4E264iZlJ7AJ+UYcO+GxvFWT0YMTbLckgDkZk7c3qwTozdhYvXarvqx+8Ou/ kuxpQQhac/ebzxpu0N+RHSf2KIUS0g0tEGnPtGv6iL+9QNHc4JKo9Y9KKVw3tQy+Re+FQLxB 1fPE5F+qxuD3AUENpOwkMsqWLM94ohtx3CFqLpxfUPrnKFLAHOhHEbByYGvFPwIDAQABo4IC EDCCAgwwgaUGCCsGAQUFBwEBBIGYMIGVMFEGCCsGAQUFBzAChkVodHRwOi8vd3d3LnRydXN0 Y2VudGVyLmRlL2NlcnRzZXJ2aWNlcy9jYWNlcnRzL3RjX2NsYXNzMV9MMV9DQV9JWC5jcnQw QAYIKwYBBQUHMAGGNGh0dHA6Ly9vY3NwLml4LnRjY2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1 c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAU6bgoHUbP/M34TpvF7ktg69g7P9EwDAYDVR0TAQH/ BAIwADBKBgNVHSAEQzBBMD8GCSqCFAAsAQEBATAyMDAGCCsGAQUFBwIBFiRodHRwOi8vd3d3 LnRydXN0Y2VudGVyLmRlL2d1aWRlbGluZXMwDgYDVR0PAQH/BAQDAgTwMB0GA1UdDgQWBBS2 KAWfTfgJ/JQ63qLGwTXYLnI+LzBiBgNVHR8EWzBZMFegVaBThlFodHRwOi8vY3JsLml4LnRj Y2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1c3RjZW50ZXIuZGUvY3JsL3YyL3RjX0NsYXNzMV9M MV9DQV9JWC5jcmwwMwYDVR0lBCwwKgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDBwYK KwYBBAGCNxQCAjAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkqhkiG9w0B AQUFAAOCAQEAQ3bvVUpEq+cQrLpcogyt5BJNk/WvUvOHqhzyj28M9pg9hcDl1+MYl5qqj6tR GSTLPQZyf287pcmbMwbcTGZO/gbW9v7RYcut6RauWdwKMCUmKC3J4fVfDq9ZETA2WOV68ef4 B3Gzdhghsbp3Rhp5dDmrCVKAHlafm6ZwJrEQ9P76fxnQZzRLgeKpZep5ePH5YHUB3+YaOQvJ FG0bOXvfHhRiRG7/HW2G+yDgjHSxDz8AFzMWL/RFePqZ4pn6T/SM/qU6WEpW39MWyJNoH/Kx QDYK8gGYuesn1ciMCTnjrvZQj0fonGTO4SfWekJRkuGrJ7dYSZRjYbDcWBBkdFLWzzCCBdgw ggTAoAMCAQICDgboAAEAAkqWLSQM/sXJMA0GCSqGSIb3DQEBBQUAMHkxCzAJBgNVBAYTAkRF MRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSQwIgYDVQQLExtUQyBUcnVzdENlbnRl ciBVbml2ZXJzYWwgQ0ExJjAkBgNVBAMTHVRDIFRydXN0Q2VudGVyIFVuaXZlcnNhbCBDQSBJ MB4XDTA5MTEwMzE0MDgxOVoXDTI1MTIzMTIxNTk1OVowfDELMAkGA1UEBhMCREUxHDAaBgNV BAoTE1RDIFRydXN0Q2VudGVyIEdtYkgxJTAjBgNVBAsTHFRDIFRydXN0Q2VudGVyIENsYXNz IDEgTDEgQ0ExKDAmBgNVBAMTH1RDIFRydXN0Q2VudGVyIENsYXNzIDEgTDEgQ0EgSVgwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC75pBuz2Lp6QuqthDVR+V8XSsncZpozVVt 5KLv5P7yemMRwleKyH3PjmYfZUVL64Biab1GjovFblqVGCrep/EfdRonq20yU+P7TVhiLP8Z 5cegDZotIYhZhM0d8cPIij6w5d4IJM/8QCy6QSOUu4ASiTVItoYE4AFPjLqpmPwcie0fiqHH hpgmHnJla/7PZdkMZEsaCfVDEWBmJuMzVprJPT40anjG5VBLyM2I5DlsUCaeQCy2O3w3sqf1 3dyzUcv03IICuNc63towXA31Qt0TaVNU6YAmQjMepdfMbspmCZ+G8D2+xophEPPR/1vkstst smUMqX0XrLonTUJczglPAgMBAAGjggJZMIICVTCBmgYIKwYBBQUHAQEEgY0wgYowUgYIKwYB BQUHMAKGRmh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvY2VydHNlcnZpY2VzL2NhY2VydHMv dGNfdW5pdmVyc2FsX3Jvb3RfSS5jcnQwNAYIKwYBBQUHMAGGKGh0dHA6Ly9vY3NwLnRjdW5p dmVyc2FsLUkudHJ1c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAUkqR1LKSevoFE63n8isWVpesQ dXMwEgYDVR0TAQH/BAgwBgEB/wIBADBSBgNVHSAESzBJMAYGBFUdIAAwPwYJKoIUACwBAQEB MDIwMAYIKwYBBQUHAgEWJGh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvZ3VpZGVsaW5lczAO BgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFOm4KB1Gz/zN+E6bxe5LYOvYOz/RMIH9BgNVHR8E gfUwgfIwge+ggeyggemGRmh0dHA6Ly9jcmwudGN1bml2ZXJzYWwtSS50cnVzdGNlbnRlci5k ZS9jcmwvdjIvdGNfdW5pdmVyc2FsX3Jvb3RfSS5jcmyGgZ5sZGFwOi8vd3d3LnRydXN0Y2Vu dGVyLmRlL0NOPVRDJTIwVHJ1c3RDZW50ZXIlMjBVbml2ZXJzYWwlMjBDQSUyMEksTz1UQyUy MFRydXN0Q2VudGVyJTIwR21iSCxPVT1yb290Y2VydHMsREM9dHJ1c3RjZW50ZXIsREM9ZGU/ Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlPzANBgkqhkiG9w0BAQUFAAOCAQEAOcjE m+6+mO5Icm+N53G2DpCM07LBFSGoRpBoX0oE8TrJaIQh2KXmBHVdn9LU8kt3QzLclctgvwJV 0KwcsMUUl5tlCsMPpR3s2Ek5lbWpvvr0HqtW56blAQiINV9nBd1EJFASIkRjefGbV2nOq9Yz UU+N8HA7jq1ROhd/NZZraGhjthwKyfjfHV7PKxGlY+3M0MbTIG+q/GhIfm0euDpFqhKG88e9 ALXr/uoSn3MzeOcoOWjTpW3adtFO4VWVgKbgG7jNrFbvRVlHmFLbOm4msjE5aXWxLiTwpJ2X iF4zKca1vAdAOgw9us90jEtOeiH6GzjNxEMvb7TfeO6Zkuc6HDGCA84wggPKAgEBMIGPMHwx CzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQLExxU QyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRlciBD bGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wCQYFKw4DAhoFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwMTE4MDk1MDEwWjAjBgkq hkiG9w0BCQQxFgQU1RpOiulz4kW+ZHL3/+Odrcd/p7YwbAYJKoZIhvcNAQkPMV8wXTALBglg hkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBoAYJKwYBBAGCNxAEMYGSMIGP MHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQL ExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRl ciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wgaIGCyqGSIb3DQEJEAILMYGS oIGPMHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYD VQQLExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENl bnRlciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wDQYJKoZIhvcNAQEBBQAE ggEANO11SaHS/pNHgOfahbUWbbKPUehk1rFyEtJsKkofAgVQ4JAmRTgOhv6vnVCSv915I3dR uPYCaZWi8QR/lG7p1mVsjCVVSiXrGYysZ4mXnFs5TMyWQTla6FkFH6KdKLU25gbJQy1O2QXV 4enTezhwFCct+ALDMjQXS5ZbWcS3opyrslna4KNypUluj4HQ58DiLdDBnMOSvdpN3mpPheLd oH9+vHRKiPFJQQu2bVBPwWWY4cXvha3SSHRCqDKBTRAtegjTiO1Y6R57Q6vtLFyIouMKyaEA MDpbMCAUAmVcJmm1YTMtfMTjmyxiZyAU6YY7hb5ISHMGYJTuOofdpjsWBgAAAAAAAA== --------------ms090800020408080308010509--

1 0

Re: (ITS#7495) access filter not correctly validated if assertion attribute not requested
by michael＠stroeder.com 17 Jan '13

17 Jan '13

Sorry for the confusion caused by editing what I've copied from the real system before which uses a group for several Samba DC instances. In this example the ACL part should be more simple like this: access to dn.subtree="o=example" attrs=sambaNTPassword filter="(organizationalStatus=0)" by dn.exact="uid=samba_dc,o=example" write by group="cn=slapd Admins,ou=groups,o=example" =sw by self =w by * none Ciao, Michael.

1 0

(ITS#7495) access filter not correctly validated if assertion attribute not requested
by michael＠stroeder.com 17 Jan '13

17 Jan '13

Full_Name: Michael Ströder Version: RE24 6f33e2c OS: Debian Squeeze URL: Submission from: (NULL) (2001:8d8:1fe:1:d6be:d9ff:fe06:a14f) This is tested with RE24 built for Debian Squeeze: It seems that ACLs are not correctly evaluated when processing a search request if the assertion type is not requested in the search request. Example: access to dn.subtree="o=example" attrs=sambaNTPassword filter="(organizationalStatus=0)" by group="uid=samba_dc,o=example" write by group="cn=slapd Admins,ou=groups,o=example" =sw by self =w by * none The following search correctly returns attribute sambaNTPassword of the entry: ldapsearch -LLL -X "dn:uid=samba_dc,o=example" "(&(objectclass=sambaSamAccount)(uid=wtester))" organizationalStatus sambaNTPassword But this search does not return sambaNTPassword: ldapsearch -LLL -X "dn:uid=samba_dc,o=example" "(&(objectclass=sambaSamAccount)(uid=wtester))" sambaNTPassword I cannot find any hint in slapd.access(5) that this is expected behaviour.

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by hyc＠symas.com 16 Jan '13

16 Jan '13

masarati(a)aero.polimi.it wrote: >> Michael Ströder wrote: >>> hyc(a)symas.com wrote: >>>> masarati(a)aero.polimi.it wrote: >>>>> On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: >>>>> >>>>>> Please consider the attached patch which sets allowed >>>>>> "USAGE dSAOperation". This seems to be the most appropriate USAGE >>>>>> compara= >>>>>> ble >>>>>> to what's set for entryTTL in slapo-dds. >>>>> >>>>> No objection with this patch, since those properties were >>>>> "arbitrarily" >>>>> assigned to attributes defined by others to provide software >>>>> interoperability. Unless anyone has objections, I'd commit it. >>>> >>>> Go ahead. Please add a comment about the origin of the schema >>>> definitions and >>>> these interoperability concerns. >>> >>> These attribute type descriptions were roughly taken from MS AD. >> >> I meant, please add a comment *in the patch* so it will remain in the >> source code. > > There's already a detailed comment to this end in the related README, > which links the attribute definitions on <http://msdn.microsoft.com/>. As already noted, those links don't provide actual schema definitions, nor do they define the USAGE. We're making a judgement call here with no documentation to support it. We should document why we're defining it this way so we don't have to repeat this conversation again down the road. > > p. > >>> Today I've checked the subschema of a W2K8R2 AD server: >>> I did not find a single attribute type description with USAGE although >>> there >>> were attribute types formally defined in RFCs. One example is 'entryTTL' >>> defined with "USAGE dSAOperation" in RFC 2589 which in fact was >>> co-authored by >>> Microsoft employees. >>> >>> The official Microsoft documentation is here [MS-ADA1]: >>> >>> http://msdn.microsoft.com/en-us/library/cc219752.aspx >>> >>> Ciao, Michael. >>> >> >> >> >> > >

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by masarati＠aero.polimi.it 16 Jan '13

16 Jan '13

> Michael Ströder wrote: >> hyc(a)symas.com wrote: >>> masarati(a)aero.polimi.it wrote: >>>> On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: >>>> >>>>> Please consider the attached patch which sets allowed >>>>> "USAGE dSAOperation". This seems to be the most appropriate USAGE >>>>> compara= >>>>> ble >>>>> to what's set for entryTTL in slapo-dds. >>>> >>>> No objection with this patch, since those properties were >>>> "arbitrarily" >>>> assigned to attributes defined by others to provide software >>>> interoperability. Unless anyone has objections, I'd commit it. >>> >>> Go ahead. Please add a comment about the origin of the schema >>> definitions and >>> these interoperability concerns. >> >> These attribute type descriptions were roughly taken from MS AD. > > I meant, please add a comment *in the patch* so it will remain in the > source code. There's already a detailed comment to this end in the related README, which links the attribute definitions on <http://msdn.microsoft.com/>. p. >> Today I've checked the subschema of a W2K8R2 AD server: >> I did not find a single attribute type description with USAGE although >> there >> were attribute types formally defined in RFCs. One example is 'entryTTL' >> defined with "USAGE dSAOperation" in RFC 2589 which in fact was >> co-authored by >> Microsoft employees. >> >> The official Microsoft documentation is here [MS-ADA1]: >> >> http://msdn.microsoft.com/en-us/library/cc219752.aspx >> >> Ciao, Michael. >> > > > > -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by hyc＠symas.com 16 Jan '13

16 Jan '13

Michael Ströder wrote: > hyc(a)symas.com wrote: >> masarati(a)aero.polimi.it wrote: >>> On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: >>> >>>> Please consider the attached patch which sets allowed >>>> "USAGE dSAOperation". This seems to be the most appropriate USAGE compara= >>>> ble >>>> to what's set for entryTTL in slapo-dds. >>> >>> No objection with this patch, since those properties were "arbitrarily" >>> assigned to attributes defined by others to provide software >>> interoperability. Unless anyone has objections, I'd commit it. >> >> Go ahead. Please add a comment about the origin of the schema definitions and >> these interoperability concerns. > > These attribute type descriptions were roughly taken from MS AD. I meant, please add a comment *in the patch* so it will remain in the source code. > Today I've checked the subschema of a W2K8R2 AD server: > I did not find a single attribute type description with USAGE although there > were attribute types formally defined in RFCs. One example is 'entryTTL' > defined with "USAGE dSAOperation" in RFC 2589 which in fact was co-authored by > Microsoft employees. > > The official Microsoft documentation is here [MS-ADA1]: > > http://msdn.microsoft.com/en-us/library/cc219752.aspx > > Ciao, Michael. >

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by michael＠stroeder.com 16 Jan '13

16 Jan '13

hyc(a)symas.com wrote: > masarati(a)aero.polimi.it wrote: >> On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: >> >>> Please consider the attached patch which sets allowed >>> "USAGE dSAOperation". This seems to be the most appropriate USAGE compara= >>> ble >>> to what's set for entryTTL in slapo-dds. >> >> No objection with this patch, since those properties were "arbitrarily" >> assigned to attributes defined by others to provide software >> interoperability. Unless anyone has objections, I'd commit it. > > Go ahead. Please add a comment about the origin of the schema definitions and > these interoperability concerns. These attribute type descriptions were roughly taken from MS AD. Today I've checked the subschema of a W2K8R2 AD server: I did not find a single attribute type description with USAGE although there were attribute types formally defined in RFCs. One example is 'entryTTL' defined with "USAGE dSAOperation" in RFC 2589 which in fact was co-authored by Microsoft employees. The official Microsoft documentation is here [MS-ADA1]: http://msdn.microsoft.com/en-us/library/cc219752.aspx Ciao, Michael.

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by hyc＠symas.com 16 Jan '13

16 Jan '13

masarati(a)aero.polimi.it wrote: > On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: > >> Please consider the attached patch which sets allowed >> "USAGE dSAOperation". This seems to be the most appropriate USAGE compara= >> ble >> to what's set for entryTTL in slapo-dds. > > No objection with this patch, since those properties were "arbitrarily" > assigned to attributes defined by others to provide software > interoperability. Unless anyone has objections, I'd commit it. Go ahead. Please add a comment about the origin of the schema definitions and these interoperability concerns. -- -- 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#7493) slapo-allowed: allowed* attrs are replicated
by masarati＠aero.polimi.it 16 Jan '13

16 Jan '13

On 01/15/2013 07:40 PM, michael(a)stroeder.com wrote: > Please consider the attached patch which sets allowed > "USAGE dSAOperation". This seems to be the most appropriate USAGE compara= > ble > to what's set for entryTTL in slapo-dds. No objection with this patch, since those properties were "arbitrarily" assigned to attributes defined by others to provide software interoperability. Unless anyone has objections, I'd commit it. Thanks, p. -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

Re: (ITS#7490) Security weakness in sha2 password module
by quanah＠zimbra.com 15 Jan '13

15 Jan '13

--On Friday, January 11, 2013 6:19 AM +0000 mhardin(a)symas.com wrote: > Full_Name: Matthew Hardin > Version: 2.4.33+ > OS: All > URL: ftp://ftp.openldap.org/incoming/sha2.c-diff.txt > Submission from: (NULL) (69.43.206.100) > > > contrib/slapd-modules/passwd/sha2/sha2.c uses a series of context buffers > and zeros them out in several places using the following macro: > > MEMSET_BZERO(context, sizeof(context)) > > The variable 'context' is a pointer to a context buffer, so sizeof will > evaluate to the size of a pointer for the particular platform. As a > result, the context buffer is only partially zeroed. > > The correct invocation is: > > MEMSET_BZERO(context, sizeof(*context)) > > which will zero out the complete context buffer. > > The referenced diff details the changes to sha2.c that are necessary to > correct this issue. > > Note this also cleans up warnings reported by MacOS's clang compiler. > > I, Matthew Hardin, 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. Can you resubmit the patch using git-format-patch? Or at least using unified diff format? ;) --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#7493) slapo-allowed: allowed* attrs are replicated (re-sent)
by michael＠stroeder.com 15 Jan '13

15 Jan '13

This is a multi-part message in MIME format. --------------090002030703010005000105 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit (Re-sent without S/MIME signature to make ITS software happy) Please consider the attached patch which sets allowed "USAGE dSAOperation". This seems to be the most appropriate USAGE comparable to what's set for entryTTL in slapo-dds. I, Michael Ströder, hereby place the attached 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. Ciao, Michael. --------------090002030703010005000105 Content-Type: text/x-patch; name="openldap_its7493.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="openldap_its7493.patch" diff --git a/contrib/slapd-modules/allowed/allowed.c b/contrib/slapd-modules/allowed/allowed.c index b44461a..0099b70 100644 --- a/contrib/slapd-modules/allowed/allowed.c +++ b/contrib/slapd-modules/allowed/allowed.c @@ -73,7 +73,7 @@ static struct { /* added by me :) */ "DESC 'Child classes allowed for a given object' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedChildClasses }, + "USAGE dSAOperation )", &ad_allowedChildClasses }, { "( " AA_SCHEMA_AT ".912 " "NAME 'allowedChildClassesEffective' " "EQUALITY objectIdentifierMatch " @@ -81,7 +81,7 @@ static struct { /* added by me :) */ "DESC 'Child classes allowed for a given object according to ACLs' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedChildClassesEffective }, + "USAGE dSAOperation )", &ad_allowedChildClassesEffective }, { "( " AA_SCHEMA_AT ".913 " "NAME 'allowedAttributes' " "EQUALITY objectIdentifierMatch " @@ -89,7 +89,7 @@ static struct { /* added by me :) */ "DESC 'Attributes allowed for a given object' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedAttributes }, + "USAGE dSAOperation )", &ad_allowedAttributes }, { "( " AA_SCHEMA_AT ".914 " "NAME 'allowedAttributesEffective' " "EQUALITY objectIdentifierMatch " @@ -97,7 +97,7 @@ static struct { /* added by me :) */ "DESC 'Attributes allowed for a given object according to ACLs' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedAttributesEffective }, + "USAGE dSAOperation )", &ad_allowedAttributesEffective }, /* TODO: add objectClass stuff? */ --------------090002030703010005000105--

1 0

Re: (ITS#7494) dynlist overlay and DSAmanageIT control
by masarati＠aero.polimi.it 15 Jan '13

15 Jan '13

> Full_Name: Jon Kidder > Version: 2.4.33 > OS: RHEL 5.0 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (167.239.222.81) > > > I have discovered that the dynamic list overlay in 2.4.33 refuses to > supply > defined dynamic attributes when the DSAmanageIT control is present in a > search > request. How did you discover it, by reading the slapo-dynlist(5) manpage? This has been slapo-dynlist's behavior by design from the beginning. The manageDSAit control is used to inhibit dynamic list expansion and access the actual content of the entry instead (e.g. for DSAit management purposes). p. -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by michael＠stroeder.com 15 Jan '13

15 Jan '13

This is a cryptographically signed message in MIME format. --------------ms020008020506010505010302 Content-Type: multipart/mixed; boundary="------------080000060105060705050402" This is a multi-part message in MIME format. --------------080000060105060705050402 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Please consider the attached patch which sets allowed "USAGE dSAOperation". This seems to be the most appropriate USAGE compara= ble to what's set for entryTTL in slapo-dds. I, Michael Str=F6der, hereby place the attached modifications to OpenLDAP= Software (and only these modifications) into the public domain. Hence, th= ese modifications may be freely used and/or redistributed for any purpose wit= h or without attribution and/or other notice. Ciao, Michael. --------------080000060105060705050402 Content-Type: text/x-patch; name="openldap_its7493.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="openldap_its7493.patch" diff --git a/contrib/slapd-modules/allowed/allowed.c b/contrib/slapd-modu= les/allowed/allowed.c index b44461a..0099b70 100644 --- a/contrib/slapd-modules/allowed/allowed.c +++ b/contrib/slapd-modules/allowed/allowed.c @@ -73,7 +73,7 @@ static struct { /* added by me :) */ "DESC 'Child classes allowed for a given object' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedChildClasses }, + "USAGE dSAOperation )", &ad_allowedChildClasses }, { "( " AA_SCHEMA_AT ".912 " "NAME 'allowedChildClassesEffective' " "EQUALITY objectIdentifierMatch " @@ -81,7 +81,7 @@ static struct { /* added by me :) */ "DESC 'Child classes allowed for a given object according to ACLs' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedChildClassesEffective }, + "USAGE dSAOperation )", &ad_allowedChildClassesEffective }, { "( " AA_SCHEMA_AT ".913 " "NAME 'allowedAttributes' " "EQUALITY objectIdentifierMatch " @@ -89,7 +89,7 @@ static struct { /* added by me :) */ "DESC 'Attributes allowed for a given object' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedAttributes }, + "USAGE dSAOperation )", &ad_allowedAttributes }, { "( " AA_SCHEMA_AT ".914 " "NAME 'allowedAttributesEffective' " "EQUALITY objectIdentifierMatch " @@ -97,7 +97,7 @@ static struct { /* added by me :) */ "DESC 'Attributes allowed for a given object according to ACLs' " "NO-USER-MODIFICATION " - "USAGE directoryOperation )", &ad_allowedAttributesEffective }, + "USAGE dSAOperation )", &ad_allowedAttributesEffective }, =20 /* TODO: add objectClass stuff? */ =20 --------------080000060105060705050402-- --------------ms020008020506010505010302 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCC BT8wggQnoAMCAQICDwCmSwABAAIAivjZQ8SBvzANBgkqhkiG9w0BAQUFADB8MQswCQYDVQQG EwJERTEcMBoGA1UEChMTVEMgVHJ1c3RDZW50ZXIgR21iSDElMCMGA1UECxMcVEMgVHJ1c3RD ZW50ZXIgQ2xhc3MgMSBMMSBDQTEoMCYGA1UEAxMfVEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBM MSBDQSBJWDAeFw0xMjA2MDYxOTAyMTZaFw0xMzA2MDcxOTAyMTZaMCgxCzAJBgNVBAYTAkRF MRkwFwYDVQQDDBBNaWNoYWVsIFN0csO2ZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAxXZGav40rnGNLxEggBW94MILWHlfC8a23Jew5U1gPlfRTXOjjzmoaZ1uCyGdgF6M VvuO9T1aTQNGH+OdeGe3P7Tfc/NsLJFJ2wtd8blvhmodUgse2eypiWjNOd4gZuhalBhgsQ0K b5D6/1foghII4E264iZlJ7AJ+UYcO+GxvFWT0YMTbLckgDkZk7c3qwTozdhYvXarvqx+8Ou/ kuxpQQhac/ebzxpu0N+RHSf2KIUS0g0tEGnPtGv6iL+9QNHc4JKo9Y9KKVw3tQy+Re+FQLxB 1fPE5F+qxuD3AUENpOwkMsqWLM94ohtx3CFqLpxfUPrnKFLAHOhHEbByYGvFPwIDAQABo4IC EDCCAgwwgaUGCCsGAQUFBwEBBIGYMIGVMFEGCCsGAQUFBzAChkVodHRwOi8vd3d3LnRydXN0 Y2VudGVyLmRlL2NlcnRzZXJ2aWNlcy9jYWNlcnRzL3RjX2NsYXNzMV9MMV9DQV9JWC5jcnQw QAYIKwYBBQUHMAGGNGh0dHA6Ly9vY3NwLml4LnRjY2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1 c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAU6bgoHUbP/M34TpvF7ktg69g7P9EwDAYDVR0TAQH/ BAIwADBKBgNVHSAEQzBBMD8GCSqCFAAsAQEBATAyMDAGCCsGAQUFBwIBFiRodHRwOi8vd3d3 LnRydXN0Y2VudGVyLmRlL2d1aWRlbGluZXMwDgYDVR0PAQH/BAQDAgTwMB0GA1UdDgQWBBS2 KAWfTfgJ/JQ63qLGwTXYLnI+LzBiBgNVHR8EWzBZMFegVaBThlFodHRwOi8vY3JsLml4LnRj Y2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1c3RjZW50ZXIuZGUvY3JsL3YyL3RjX0NsYXNzMV9M MV9DQV9JWC5jcmwwMwYDVR0lBCwwKgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDBwYK KwYBBAGCNxQCAjAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkqhkiG9w0B AQUFAAOCAQEAQ3bvVUpEq+cQrLpcogyt5BJNk/WvUvOHqhzyj28M9pg9hcDl1+MYl5qqj6tR GSTLPQZyf287pcmbMwbcTGZO/gbW9v7RYcut6RauWdwKMCUmKC3J4fVfDq9ZETA2WOV68ef4 B3Gzdhghsbp3Rhp5dDmrCVKAHlafm6ZwJrEQ9P76fxnQZzRLgeKpZep5ePH5YHUB3+YaOQvJ FG0bOXvfHhRiRG7/HW2G+yDgjHSxDz8AFzMWL/RFePqZ4pn6T/SM/qU6WEpW39MWyJNoH/Kx QDYK8gGYuesn1ciMCTnjrvZQj0fonGTO4SfWekJRkuGrJ7dYSZRjYbDcWBBkdFLWzzCCBdgw ggTAoAMCAQICDgboAAEAAkqWLSQM/sXJMA0GCSqGSIb3DQEBBQUAMHkxCzAJBgNVBAYTAkRF MRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSQwIgYDVQQLExtUQyBUcnVzdENlbnRl ciBVbml2ZXJzYWwgQ0ExJjAkBgNVBAMTHVRDIFRydXN0Q2VudGVyIFVuaXZlcnNhbCBDQSBJ MB4XDTA5MTEwMzE0MDgxOVoXDTI1MTIzMTIxNTk1OVowfDELMAkGA1UEBhMCREUxHDAaBgNV BAoTE1RDIFRydXN0Q2VudGVyIEdtYkgxJTAjBgNVBAsTHFRDIFRydXN0Q2VudGVyIENsYXNz IDEgTDEgQ0ExKDAmBgNVBAMTH1RDIFRydXN0Q2VudGVyIENsYXNzIDEgTDEgQ0EgSVgwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC75pBuz2Lp6QuqthDVR+V8XSsncZpozVVt 5KLv5P7yemMRwleKyH3PjmYfZUVL64Biab1GjovFblqVGCrep/EfdRonq20yU+P7TVhiLP8Z 5cegDZotIYhZhM0d8cPIij6w5d4IJM/8QCy6QSOUu4ASiTVItoYE4AFPjLqpmPwcie0fiqHH hpgmHnJla/7PZdkMZEsaCfVDEWBmJuMzVprJPT40anjG5VBLyM2I5DlsUCaeQCy2O3w3sqf1 3dyzUcv03IICuNc63towXA31Qt0TaVNU6YAmQjMepdfMbspmCZ+G8D2+xophEPPR/1vkstst smUMqX0XrLonTUJczglPAgMBAAGjggJZMIICVTCBmgYIKwYBBQUHAQEEgY0wgYowUgYIKwYB BQUHMAKGRmh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvY2VydHNlcnZpY2VzL2NhY2VydHMv dGNfdW5pdmVyc2FsX3Jvb3RfSS5jcnQwNAYIKwYBBQUHMAGGKGh0dHA6Ly9vY3NwLnRjdW5p dmVyc2FsLUkudHJ1c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAUkqR1LKSevoFE63n8isWVpesQ dXMwEgYDVR0TAQH/BAgwBgEB/wIBADBSBgNVHSAESzBJMAYGBFUdIAAwPwYJKoIUACwBAQEB MDIwMAYIKwYBBQUHAgEWJGh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvZ3VpZGVsaW5lczAO BgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFOm4KB1Gz/zN+E6bxe5LYOvYOz/RMIH9BgNVHR8E gfUwgfIwge+ggeyggemGRmh0dHA6Ly9jcmwudGN1bml2ZXJzYWwtSS50cnVzdGNlbnRlci5k ZS9jcmwvdjIvdGNfdW5pdmVyc2FsX3Jvb3RfSS5jcmyGgZ5sZGFwOi8vd3d3LnRydXN0Y2Vu dGVyLmRlL0NOPVRDJTIwVHJ1c3RDZW50ZXIlMjBVbml2ZXJzYWwlMjBDQSUyMEksTz1UQyUy MFRydXN0Q2VudGVyJTIwR21iSCxPVT1yb290Y2VydHMsREM9dHJ1c3RjZW50ZXIsREM9ZGU/ Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlPzANBgkqhkiG9w0BAQUFAAOCAQEAOcjE m+6+mO5Icm+N53G2DpCM07LBFSGoRpBoX0oE8TrJaIQh2KXmBHVdn9LU8kt3QzLclctgvwJV 0KwcsMUUl5tlCsMPpR3s2Ek5lbWpvvr0HqtW56blAQiINV9nBd1EJFASIkRjefGbV2nOq9Yz UU+N8HA7jq1ROhd/NZZraGhjthwKyfjfHV7PKxGlY+3M0MbTIG+q/GhIfm0euDpFqhKG88e9 ALXr/uoSn3MzeOcoOWjTpW3adtFO4VWVgKbgG7jNrFbvRVlHmFLbOm4msjE5aXWxLiTwpJ2X iF4zKca1vAdAOgw9us90jEtOeiH6GzjNxEMvb7TfeO6Zkuc6HDGCA84wggPKAgEBMIGPMHwx CzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQLExxU QyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRlciBD bGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wCQYFKw4DAhoFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwMTE1MTg0MDAwWjAjBgkq hkiG9w0BCQQxFgQUpoVTENSoP9NXF741WIXk6TTjK0gwbAYJKoZIhvcNAQkPMV8wXTALBglg hkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBoAYJKwYBBAGCNxAEMYGSMIGP MHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQL ExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRl ciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wgaIGCyqGSIb3DQEJEAILMYGS oIGPMHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYD VQQLExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENl bnRlciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wDQYJKoZIhvcNAQEBBQAE ggEAnErBsB1Irvgi6SFHujzKoEbcOV6VxNDlc7dGSZtr55YPnJ0vvZjPOpXpQ/o+SpeUswFp dLLv1RSwdL/ahZ9L5FFVMcbX9khvD+1beRYFFkhGg/UuVHEQWdZnRRacUT+v93tj9t4Sr526 Wcn7K0if4KtLCkPh0sh4MilBSLScENbWJppsr2sq/K5zy9R0u1XAev2R2qnhlsdnCEqfoLQ3 gISQIM+wmAbn+Az6TYw/vabVYA/pKM4Fbiah3sRfrItVPDMOzYm59CyfjFrjvTSZcH93lUmx iC3GYilhfuyHS9RxO6wIbIjje41x4+Ogm/3FSgfPl6IkiOZepAMHHeiXOQAAAAAAAA== --------------ms020008020506010505010302--

1 0

(ITS#7494) dynlist overlay and DSAmanageIT control
by jckidder＠aep.com 15 Jan '13

15 Jan '13

Full_Name: Jon Kidder Version: 2.4.33 OS: RHEL 5.0 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (167.239.222.81) I have discovered that the dynamic list overlay in 2.4.33 refuses to supply defined dynamic attributes when the DSAmanageIT control is present in a search request.

1 0

Re: (ITS#7493) slapo-allowed: allowed* attrs are replicated
by michael＠stroeder.com 15 Jan '13

15 Jan '13

On Tue, 15 Jan 2013 13:37:06 GMT masarati(a)aero.polimi.it wrote > Their value depends on ACLs, so in order to reflect ACLs on a specific > DSA they should be generated; however, I concur ACLs should not depend > on the specific DSA of a replication setup. BTW: It does make sense to have different ACLs on different replicas! Think of a master with fine-grained ACLs for entry management and read-only consumers with simpler ACLs for better performance. Ciao, Michael.

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