- openldap-bugs - openldap.org

(ITS#6717) syncprov performs unnecessary presentations/refreshes.
by cmikk＠qwest.net 20 Nov '10

20 Nov '10

Full_Name: Chris Mikkelson Version: 2.4.23 OS: FreeBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (204.147.85.37) I have a multimaster setup, and some read-only slaves mirroring the data with syncrepl. In some circumstances, I've noticed that restarting a slave server leads to a full presentation, even though the masters have an adequately sized sessionlog. This makes refreshOnly synchronization prohibitively expensive. It appears that the problem is as follows: The syncprov overlay uses the minimum CSN from the client cookie to decide where to start synchronization, regardless of whether that CSN has changed relative to the same SID's CSN on the provider. For example: Provider state: CSN: <1 second ago>...#001#... CSN: <1 year ago>.....#002#... sessionlog mincsn: <1 hour ago>...#001#... Consumer state: CSN: <1 minute ago>...#001#... CSN: <1 year ago>.....#002#... <-- same as SID 2 CSN on provider The syncprov overly will take the mincsn from the consumer cookie (the <1 year ago> one above) and compare it to the sessionlog mincsn when deciding whether to do a full presentation. Since the SID 2 CSN hasn't changed in the above example, the consumer is up to date on changes recorded on SID 2, so the SID 1 CSN from the cookie should be used. To reproduce: * Set up slapd servers ID 1 and 2 as multimaster nodes, and a third slapd server replicating from server 1. * Insert one entry into server ID 2, and restart servers 1 and 2. * Insert entries into Server ID 1. * Perform enough modifications / deletions on Server ID 1 to cause entries to be purged from the sessionlog (see ITS #6716). * Wait for slave to catch up, then stop the slave. * Do any modification on Server ID 1 (only need to change the SID 1 contextCSN) * Restart slave. Server will present entries to the slave rather than replaying the session log.

1 0

(ITS#6716) syncprov sessionlog 'sl_mincsn' not assigned a value.
by cmikk＠qwest.net 19 Nov '10

19 Nov '10

Full_Name: Chris Mikkelson Version: 2.4.23 OS: FreeBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (204.147.85.37) On line 2875 of servers/slapd/overlays/syncprov.c (release 2.4.23), the sessionlog mincsn is initialized to a zero-length value. if ( !sl ) { sl = ch_malloc( sizeof( sessionlog ) + LDAP_PVT_CSNSTR_BUFSIZE ); sl->sl_mincsn.bv_val = (char *)(sl+1); sl->sl_mincsn.bv_len = 0; sl->sl_num = 0; sl->sl_head = sl->sl_tail = NULL; ldap_pvt_thread_mutex_init( &sl->sl_mutex ); si->si_logs = sl; } >From there, sl->sl_mincsn isn't touched until log entries are purged from the sessionlog on line 1522: while ( sl->sl_num > sl->sl_size ) { se = sl->sl_head; sl->sl_head = se->se_next; strcpy( sl->sl_mincsn.bv_val, se->se_csn.bv_val ); sl->sl_mincsn.bv_len = se->se_csn.bv_len; ch_free( se ); sl->sl_num--; } So, after the sessionlog has its first entry recorded and before it has its first entry received, sl->sl_mincsn is a zero-length value, which means the following comparison on line 2536: if ( sl->sl_num > 0 && ber_bvcmp( &mincsn, &sl->sl_mincsn ) >= 0 ) { do_present = 0; will evaluate to true in cases where it should not. A quick fix would be to compare directly against the CSN of the sessionlog's head: --- syncprov.c.orig 2010-11-17 14:07:26.000000000 -0600 +++ syncprov.c 2010-11-19 16:50:58.000000000 -0600 @@ -2533,7 +2533,7 @@ /* Are there any log entries, and is the consumer state * present in the session log? */ - if ( sl->sl_num > 0 && ber_bvcmp( &mincsn, &sl->sl_mincsn ) >= 0 ) { + if ( sl->sl_num > 0 && ber_bvcmp( &mincsn, &sl->sl_head->se_csn ) >= 0 ) { do_present = 0; /* mutex is unlocked in playlog */ syncprov_playlog( op, rs, sl, srs, ctxcsn, numcsns, sids );

1 0

Re: ITS#6713
by masarati＠aero.polimi.it 19 Nov '10

19 Nov '10

DevMan wrote: > Please let me know the upgradation procedure. <http://www.openldap.org/doc/admin24/install.html> In general, <http://www.openldap.org/doc/admin24/index.html> p.

1 0

Re: ITS#6713
by devman1624＠yahoo.com 19 Nov '10

19 Nov '10

Please let me know the upgradation procedure. Thx DevMan Sent from my iPhone On Nov 18, 2010, at 3:33 PM, Pierangelo Masarati <masarati(a)aero.polimi.it> w= rote: > Please note that the current release is 2.4.23; since 2.4.16 many issues h= ave been fixed. If the problem persists after upgrading, please make sure y= ou provide useful information, as illustrated here <http://www.openldap.org/= faq/data/cache/56.html> and in subordinate links. >=20 > p.

1 0

(ITS#6715) Broken 'sortvals' for attr with 1 value
by h.b.furuseth＠usit.uio.no 19 Nov '10

19 Nov '10

Full_Name: Hallvard B Furuseth Version: 2.4.23 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (129.240.6.233) Submitted by: hallvard slapd.conf:'sortvals ATTR' sometimes complains attributeType ATTR value #1 provided more than once when ATTR has one value, because slapd/modify.c:slap_sort_vals() then leaves the result value 'rc' uninitialized. Fixing.

1 0

(ITS#6714) Patch - Mozilla NSS - implement full non-blocking semantics
by rmeggins＠redhat.com 18 Nov '10

18 Nov '10

Full_Name: Rich Megginson Version: 2.4.23 (current CVS HEAD) OS: RHEL6 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-use-non-blocking-semantics-… Submission from: (NULL) (76.113.111.209) This patch implements full non-blocking semantics for the MozNSS crypto implementation in the same manner as the openssl and gnutls implementations. SSL_ForceHandshake can be called repeatedly until it gets enough data to complete. One wrinkle is that, when SSL_ForceHandshake returns PR_WOULD_BLOCK_ERROR, we have no way of knowing if it needs data for a read or a write (a la openssl SSL_ERROR_WANT_WRITE and SSL_ERROR_WANT_READ). In order to keep track of that, we use the io_flag in the tls_data object - if the last operation called was a read/recv, we set the io_flag to TLSM_READ, and similar for send/write and TLSM_WRITE. This way, the upflags function knows how to set the sbiod needs_read and needs_write flags appropriately. I also added special handling for the common case where the client uses ldapTOOL -Z and the TLS fails from the client side (e.g. bogus CA cert file). In this case, tlsm_session_accept will get a plain LDAP message beginning with LBER_SEQUENCE instead of a valid SSL header. The code can short circuit the process and return a more meaningful error message. The tlsm_is_io_ready() function is now obsolete - keeping track of the io_flag, plus using the function SSL_DataPending(), removes the need for the former function. I added a convenience function tlsm_get_pvt_tls_data() to get the tls_data associated with the tlsm_session (secure PRFileDesc). This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

ITS#6712
by masarati＠aero.polimi.it 18 Nov '10

18 Nov '10

Thanks for the report. "hasSubordinates" is generated, not stored in the database; this may explain why multiple values appear despite its "single-valuedness". I'm investigating... p.

1 0

ITS#6713
by masarati＠aero.polimi.it 18 Nov '10

18 Nov '10

Please note that the current release is 2.4.23; since 2.4.16 many issues have been fixed. If the problem persists after upgrading, please make sure you provide useful information, as illustrated here <http://www.openldap.org/faq/data/cache/56.html> and in subordinate links. p.

1 0

(ITS#6713) slad crashing automatically in production server
by devman1624＠yahoo.com 18 Nov '10

18 Nov '10

Full_Name: DevMan Version: 2.4.16 OS: RHEL5.4 64 bit URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (12.191.136.3) Hi All, I am facing issue in my prod server. PLease find the below details: DS: Openldap2.4.16(2 Multimaster with one slave) Database: BDB4.7.25 OS: RHEL5.4 64 bit Number of databases: 2 Number of entries in one database is 9lakhs and in second database is 2000. RAM: 2GB CPU: 2(Model name: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz) Issue: slapd automatically killed once in a day or some time 3 in a day. I have run the below command and found segfault error 4: [root@MYINSGGNSBILDAP2 openldap]# dmesg |grep slapd slapd[30387]: segfault at 0000000000000017 rip 00000000004dca25 rsp 00007fff61425f80 error 4 slapd[32121]: segfault at 0000000000000048 rip 0000003cd8008950 rsp 0000000042554948 error 4 slapd[1013]: segfault at 0000000000000048 rip 0000003cd8008950 rsp 000000004233c948 error 4 slapd[13060]: segfault at 0000000000000000 rip 0000003cd747997a rsp 00000000422408e8 error 4 slapd[24417]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000046333560 error 4 slapd[694]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000043cfa560 error 4 slapd[1068]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000041446560 error 4 slapd[5557]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000041fd2560 error 4 slapd[15633]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000041a9d560 error 4 slapd[31922]: segfault at 0000000000000008 rip 000000000048d6b2 rsp 0000000043312560 error 4 slapd[13961]: segfault at 0000000000000000 rip 0000003cd747997a rsp 000000004230f4e8 error 4 slapd[14807]: segfault at 0000000000000048 rip 0000003cd8008950 rsp 0000000041523948 error 4 Please help me here to resolve this problem. Thx DevMan

1 0

(ITS#6712) dont-use-copy/syncrepl/chain hasSubordinates extra vals
by david.delaharpe.golden＠ichec.ie 17 Nov '10

17 Nov '10

Full_Name: David De La Harpe Golden (ICHEC) Version: 2.4.23 OS: debian/unstable URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.1.200.66) I was playing with the experimental "dont-use-copy" ldap control in conjunction with a basic test provider-consumer syncrepl setup and chain overlay back to the provider on the consumer. I realise the control is experimental and the issue is not major, but anyway, better to report these things: Seems that when the control is used in a search request to the consumer, hasSubordinates on the returned value is getting extra values. As hasSubordinates is AFAICS defined as a single-value attribute, that's strange. # e.g. Test using python-ldap import ldap from ldap.controls import LDAPControl class _ExpDontUseCopyControl(LDAPControl): controlType = '1.3.6.1.4.1.4203.666.5.15' provider = ldap.open('localhost', 3389) consumer = ldap.open('localhost', 389) provider.bind('cn=something,dc=example,dc=com', 'somepw') consumer.bind('cn=something,dc=example,dc=com', 'somepw') provider.search_ext_s('cn=foo,dc=example,dc=com', ldap.SCOPE_BASE, '(objectClass=*)', ['hasSubordinates'], serverctrls=[]) => [('cn=foo,dc=example,dc=com', {'hasSubordinates': ['FALSE']})] provider.search_ext_s('cn=foo,dc=example,dc=com', ldap.SCOPE_BASE, '(objectClass=*)', ['hasSubordinates'], serverctrls=[_ExpDontUseCopyControl(True)]) => [('cn=foo,dc=example,dc=com', {'hasSubordinates': ['FALSE']})] consumer.search_ext_s('cn=foo,dc=example,dc=com', ldap.SCOPE_BASE, '(objectClass=*)', ['hasSubordinates'], serverctrls=[]) => [('cn=foo,dc=example,dc=com', {'hasSubordinates': ['FALSE']})] consumer.search_ext_s('cn=foo,dc=example,dc=com', ldap.SCOPE_BASE, '(objectClass=*)', ['hasSubordinates'], serverctrls=[_ExpDontUseCopyControl(True)]) => [('cn=foo,dc=example,dc=com', {'hasSubordinates': ['FALSE', 'FALSE']})]

1 0

(ITS#6711) Problems with ppolicy_forward_updates and starttls with certificate-based auth
by subbarao＠computer.org 17 Nov '10

17 Nov '10

Full_Name: Kartik Subbarao Version: 2.4.23 OS: Debian Linux 5.0.5 URL: ftp://ftp.openldap.org/incoming/kartik_subbarao.101116.tgz Submission from: (NULL) (76.99.175.5) I'm trying to get a consumer server to forward ppolicy-related updates to its provider server, and to use certificate-based authentication (SASL EXTERNAL) over STARTTLS when authenticating to the provider. I'm running into multiple problems here. The core problem seems to be that enabling ppolicy_forward_updates breaks the chaining overlay such that it binds anonymously instead of with SASL EXTERNAL. Another problem is that bind operations to the consumer server start to return two result messages -- one with the error code of the chained operation, and one with the error code of the bind operation. To simplify reproducing the problem, I've worked with test022-ppolicy in the openldap test framework. Here, I ran into another issue. I can't seem to be able to configure sasl external/starttls chaining properly with the cn=config style configuration that test022-ppolicy applies. The self-signed cert that I'm using works fine with replication, but it doesn't seem to work with chaining. This may or may not be another issue that needs to be resolved. In any case, with the attached files in the ITS, I hope that what I'm trying to do and the results that I'm getting should be as clear as possible.

1 0

Re: (ITS#6703) Patch - Mozilla NSS - reject non-file key and cert files
by rmeggins＠redhat.com 15 Nov '10

15 Nov '10

On 11/15/2010 01:22 PM, Howard Chu wrote: > rmeggins(a)redhat.com wrote: >> On 11/15/2010 12:39 PM, Howard Chu wrote: >>> rmeggins(a)redhat.com wrote: >>>> Full_Name: Rich Megginson >>>> Version: 2.4.23 (current CVS HEAD) >>>> OS: RHEL5 >>>> URL: >>>> ftp://ftp.openldap.org/incoming/openldap-2.4.23-reject_non_file_key_cert_pe… >>>> >>>> Submission from: (NULL) (76.113.111.209) >>>> >>>> >>>> If you specify a directory instead of a file to TLS_CACERT, or if one >>>> of the >>>> items in the TLS_CACERTDIR is a directory, the NSS PEM reader will >>>> crash. This >>>> patch rejects any item which looks like a directory. >>> >>> It sounds like this is a bug that ought to be patched in the NSS PEM >>> reader instead, no? >>> >> Yes, you are correct. I have filed this bug - >> https://bugzilla.redhat.com/show_bug.cgi?id=653619 >> But the patch to openldap will allow it to bypass this problem. > > OK. I've reviewed and committed all of your patches 6703-6706. > Thanks!

1 0

Re: (ITS#6703) Patch - Mozilla NSS - reject non-file key and cert files
by hyc＠symas.com 15 Nov '10

15 Nov '10

rmeggins(a)redhat.com wrote: > On 11/15/2010 12:39 PM, Howard Chu wrote: >> rmeggins(a)redhat.com wrote: >>> Full_Name: Rich Megginson >>> Version: 2.4.23 (current CVS HEAD) >>> OS: RHEL5 >>> URL: >>> ftp://ftp.openldap.org/incoming/openldap-2.4.23-reject_non_file_key_cert_pe… >>> Submission from: (NULL) (76.113.111.209) >>> >>> >>> If you specify a directory instead of a file to TLS_CACERT, or if one >>> of the >>> items in the TLS_CACERTDIR is a directory, the NSS PEM reader will >>> crash. This >>> patch rejects any item which looks like a directory. >> >> It sounds like this is a bug that ought to be patched in the NSS PEM >> reader instead, no? >> > Yes, you are correct. I have filed this bug - > https://bugzilla.redhat.com/show_bug.cgi?id=653619 > But the patch to openldap will allow it to bypass this problem. OK. I've reviewed and committed all of your patches 6703-6706. -- -- 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#6703) Patch - Mozilla NSS - reject non-file key and cert files
by rmeggins＠redhat.com 15 Nov '10

15 Nov '10

On 11/15/2010 12:39 PM, Howard Chu wrote: > rmeggins(a)redhat.com wrote: >> Full_Name: Rich Megginson >> Version: 2.4.23 (current CVS HEAD) >> OS: RHEL5 >> URL: >> ftp://ftp.openldap.org/incoming/openldap-2.4.23-reject_non_file_key_cert_pe… >> Submission from: (NULL) (76.113.111.209) >> >> >> If you specify a directory instead of a file to TLS_CACERT, or if one >> of the >> items in the TLS_CACERTDIR is a directory, the NSS PEM reader will >> crash. This >> patch rejects any item which looks like a directory. > > It sounds like this is a bug that ought to be patched in the NSS PEM > reader instead, no? > Yes, you are correct. I have filed this bug - https://bugzilla.redhat.com/show_bug.cgi?id=653619 But the patch to openldap will allow it to bypass this problem.

1 0

Re: (ITS#6703) Patch - Mozilla NSS - reject non-file key and cert files
by hyc＠symas.com 15 Nov '10

15 Nov '10

rmeggins(a)redhat.com wrote: > Full_Name: Rich Megginson > Version: 2.4.23 (current CVS HEAD) > OS: RHEL5 > URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-reject_non_file_key_cert_pe… > Submission from: (NULL) (76.113.111.209) > > > If you specify a directory instead of a file to TLS_CACERT, or if one of the > items in the TLS_CACERTDIR is a directory, the NSS PEM reader will crash. This > patch rejects any item which looks like a directory. It sounds like this is a bug that ought to be patched in the NSS PEM reader instead, 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

(ITS#6710) Mods already refreshed on a forwarding server is lost by its consumer
by rein＠OpenLDAP.org 15 Nov '10

15 Nov '10

Full_Name: Rein Tollevik Version: CVS head OS: Irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.215.59.121) Submitted by: rein New syncprov consumers connecting to a forwarding server and presenting an apperently up-to-date cookie will loose any mods that have already taken place on the forwarding server if it itself is refreshing from its provider. This should not be a problem if the forwarding server have a sufficiently large syncprov log, but a fix for servers without is coming. -- Rein Tollevik Basefarm AS

1 0

(ITS#6709) Active mods not replicated to new consumers
by rein＠OpenLDAP.org 15 Nov '10

15 Nov '10

Full_Name: Rein Tollevik Version: CVS head OS: Irrelevant URL: Submission from: (NULL) (84.215.59.121) Submitted by: rein New syncprov consumers connecting when there are active mods risk loosing these mods, where an active mod is any mod that have called syncprov_op_mod() but not yet the syncprov_op_response() or syncprov_op_cleanup() callbacks. A fix is coming. -- Rein Tollevik Basefarm AS

1 0

Re: (ITS#6693) Value dependent ACL issues
by rhafer＠suse.de 15 Nov '10

15 Nov '10

I just submitted the fix to HEAD. The changes are in: servers/slapd/acl.c r1.355 servers/slapd/slap.h r1.898 Ralf

1 0

(ITS#6708) Race condition fixing syncprov filter
by rein＠OpenLDAP.org 15 Nov '10

15 Nov '10

Full_Name: Rein Tollevik Version: CVS head OS: Irrelevant URL: Submission from: (NULL) (84.215.59.121) Submitted by: rein In ITS#6555 a fix to skip the and/ge filter stuck in front of the consumers filter was added, but this left a race condition between modifying the filter and noting it in the flags. There is a race both when the filter is stuck in the front and when it gets removed again when the op is detached. A fix is coming. -- Rein Tollevik Basefarm AS

1 0

(ITS#6707) Syncrepl may reuse presentlist
by rein＠OpenLDAP.org 15 Nov '10

15 Nov '10

Full_Name: Rein Tollevik Version: CVS head OS: Irrelevant URL: Submission from: (NULL) (84.215.59.121) Submitted by: rein If syncrepl gets interrupted during the present phase it may reuse the presentlist on the next connection. Any entries in the list that gets deleted on the provider in mean time will not be deleted on the consumer. A fix is coming. -- Rein Tollevik Basefarm AS

1 0

Re: (ITS#6556) test031 core dumps after applying first filter
by ian＠uns.ac.rs 15 Nov '10

15 Nov '10

slap_sl_free dumps core here because it gets passed a bogus bv_val (from the ma_value field of an instance of struct MatchingRuleAssertion). As far as I can see, the original bv_val gets clobbered in get_comp_filter (servers/slapd/component.c), line 350: bv->bv_val = cav.cav_ptr; Commenting that line out fixes the core dump. I suspect that the assignment is there to support nested component filters (see lines 1039 et seq. in the same file). Earlier versions of OpenLDAP had different logic in slap_sl_free, which skipped the offending pointer (and thus probably leaving a memory leak). i.

1 0

(ITS#6706) Patch - Mozilla NSS - improve trace messages
by rmeggins＠redhat.com 12 Nov '10

12 Nov '10

Full_Name: Rich Megginson Version: 2.4.23 (current CVS HEAD) OS: RHEL5 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-improve_trace_messages-2010… Submission from: (NULL) (76.113.111.209) The trace messages from tls_m.c are unhelpful and misleading in many cases. SSL_SecurityStatus() only works after the first handshake is complete, so use a handshake callback to print that information instead. Since tlsm_session_chkhost handles the SSL_ERROR_BAD_CERT_DOMAIN case, we don't need to print out a message for that error. This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

Re: (ITS#6705) Patch - Mozilla NSS - should only use
by rmeggins＠redhat.com 12 Nov '10

12 Nov '10

This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

(ITS#6705) Patch - Mozilla NSS - should only use ".0" files in cacertdir
by rmeggins＠redhat.com 12 Nov '10

12 Nov '10

Full_Name: Rich Megginson Version: 2.4.23 (current CVS HEAD) OS: RHEL5 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-look_only_for_.0_cacertdir_… Submission from: (NULL) (76.113.111.209) When cacertdir is specified, only the files that have openssl c_hash hashed file names ending in ".0" should be used.

1 0

(ITS#6704) Patch - Mozilla NSS - use both cacert and cacertdir
by rmeggins＠redhat.com 12 Nov '10

12 Nov '10

Full_Name: Rich Megginson Version: 2.4.23 (current CVS HEAD) OS: RHEL5 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-use_both_cacert_and_cacertd… Submission from: (NULL) (76.113.111.209) The code should attempt to use both TLS_CACERT and TLS_CACERTDIR if both are specified. This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

(ITS#6703) Patch - Mozilla NSS - reject non-file key and cert files
by rmeggins＠redhat.com 12 Nov '10

12 Nov '10

Full_Name: Rich Megginson Version: 2.4.23 (current CVS HEAD) OS: RHEL5 URL: ftp://ftp.openldap.org/incoming/openldap-2.4.23-reject_non_file_key_cert_pe… Submission from: (NULL) (76.113.111.209) If you specify a directory instead of a file to TLS_CACERT, or if one of the items in the TLS_CACERTDIR is a directory, the NSS PEM reader will crash. This patch rejects any item which looks like a directory. This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Rich Megginson am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

Re: (ITS#6702) slappasswd prompts missing
by d＠delphij.net 12 Nov '10

12 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 11/11/10 20:51, David Gessel wrote: > Excellent. > > Xin Li had a partial patch earlier tonight that got the prompts directed properly to console. Thanks. To Howard, I think getpassphrase(3) is Solaris specific interface and not part of standard. On FreeBSD, getpass(3) returns a buffer pointer that contains at most 128 (_PASSWORD_LEN) characters, which should fulfill the need of OpenBSD but shorter than Solaris[1] which have 256, not counting the terminating nul character. Note that FreeBSD do have a readpassphrase(3) extension which provide more flexibility. I am not sure, however, whether we should implement the Solaris behavior for getpassphrase(3), as it's not a standard defined interface? Is there any other operating system that provide getpassphrase(3) and have the same behavior? If it's desirable we could have it implemented on FreeBSD this way: ================= char * getpassrase(const char *prompt) { static char buf[256 + 1]; return(readpassphrase(prompt, buf, sizeof(buf), RPP_ECHO_OFF)); } ================= Please advise, thanks! [1] http://docs.sun.com/app/docs/doc/816-5168/getpassphrase-3c?l=en&n=1&a=view > -------- Original Message -------- > Subject: Re: (ITS#6702) slappasswd prompts missing > From: Howard Chu <hyc(a)symas.com> > To: gessel(a)blackrosetech.com > Date: Thu Nov 11 2010 19:18:29 GMT-0800 (Pacific Standard Time) > >> Apparently FreeBSD doesn't provide a usable getpassphrase() in its libc, so a >> replacement in the OpenLDAP code is used instead. The OpenLDAP code is now >> fixed in HEAD. >> - -- Xin LI <delphij(a)delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBCAAGBQJM3YW3AAoJEATO+BI/yjfB2jsIANUBBR2Cu/uhd7w8SDmfWJkL UcibY5xL4i1gg2CM2DR/SgVqUYF/SHnGmMECgmu7CVRvXRNPn7Zp7TzhfYJgM7SJ lYqE5+uajyGUt3N3z7bB4BT9GF6PTyXhWUDsdxc1IHcQ2Dvpq/3Ih7vuCQmAimCv NJ9CXQYJPLflRo8RAMmNtiYeiZjMWK9PjrfC7CuAYKPvhKGFMQ5o7NXBZ8T+16WC Igbw7DKALAPBZmV2hXbwMQAYJ8hBUkDlph2U8k7zBTfIkWSqx+DDeY/CaOmUnb9A puUTm3WEYI2MxwlOVLnvy7QRNFsXejFvXkZN5ZTPoDbBT7MZRFrOn9gKQRGF4D8= =9iQc -----END PGP SIGNATURE-----

1 0

Re: (ITS#6702) slappasswd prompts missing
by gessel＠blackrosetech.com 12 Nov '10

12 Nov '10

Excellent. Xin Li had a partial patch earlier tonight that got the prompts directed properly to console. -------- Original Message -------- Subject: Re: (ITS#6702) slappasswd prompts missing From: Howard Chu <hyc(a)symas.com> To: gessel(a)blackrosetech.com Date: Thu Nov 11 2010 19:18:29 GMT-0800 (Pacific Standard Time) > gessel(a)blackrosetech.com wrote: >> Note: on editing slapd.conf, I see that prompt IO is directed to the file, not to the console. That is the file contains the prompts: >> "rootpw New password:" >> "Re-enter new password:" >> >> >> > Apparently FreeBSD doesn't provide a usable getpassphrase() in its libc, so a > replacement in the OpenLDAP code is used instead. The OpenLDAP code is now > fixed in HEAD. >

1 0

Re: (ITS#6702) slappasswd prompts missing
by hyc＠symas.com 12 Nov '10

12 Nov '10

gessel(a)blackrosetech.com wrote: > Note: on editing slapd.conf, I see that prompt IO is directed to the file, not to the console. That is the file contains the prompts: > "rootpw New password:" > "Re-enter new password:" > > > Apparently FreeBSD doesn't provide a usable getpassphrase() in its libc, so a replacement in the OpenLDAP code is used instead. The OpenLDAP code is now fixed in HEAD. -- -- 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#6701) Update to man8 slappasswd: English usage
by hyc＠symas.com 12 Nov '10

12 Nov '10

diver06(a)gmx.net wrote: > Full_Name: Simon Wright > Version: 2.4.23 > OS: FreeBSD > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (212.98.32.54) > > > The man page for slappasswd says that encryption scheme names need to be > protected due to "{". This is wrong usage: scheme names may need to be protected > *by* "{" Wrong. The manpage text is correct. The '{' and '}' are part of the scheme names. Since these are also meta-characters in common command shells, they may need to be protected from expansion. This ITS will be closed. -- -- 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#6702) slappasswd prompts missing
by gessel＠blackrosetech.com 11 Nov '10

11 Nov '10

Note: on editing slapd.conf, I see that prompt IO is directed to the file, not to the console. That is the file contains the prompts: "rootpw New password:" "Re-enter new password:"

1 0

(ITS#6702) slappasswd prompts missing
by gessel＠blackrosetech.com 11 Nov '10

11 Nov '10

Full_Name: David Gessel Version: openldap-sasl-server-2.4.23 OS: FreeBSD 8.1 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (66.93.181.141) Attempting to insert a hash of the root pw into slapd.conf with the command: # slappasswd >> slapd.conf yields a blank prompt, that is there is no feedback to prompt the user along the lines of: "Enter root password" and "Verify root password" But entering the root password twice with no feedback (and blank characters for security, so completely blind) gets through the command successfully.

1 0

(ITS#6701) Update to man8 slappasswd: English usage
by diver06＠gmx.net 11 Nov '10

11 Nov '10

Full_Name: Simon Wright Version: 2.4.23 OS: FreeBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.98.32.54) The man page for slappasswd says that encryption scheme names need to be protected due to "{". This is wrong usage: scheme names may need to be protected *by* "{" Patch: --- openldap-2.4.23/doc/man/man8/slappasswd.8 2010-04-13 22:22:46.000000000 +0200 +++ slappasswd.8 2010-11-11 16:36:28.000000000 +0100 @@ -100,7 +100,7 @@ The default is .BR {SSHA} . -Note that scheme names may need to be protected, due to +Note that scheme names may need to be protected by .B { and .BR } ,

1 0

Re: (ITS#6698) Please add BDB 5.x support for SLAPD
by hyc＠symas.com 11 Nov '10

11 Nov '10

faessler(a)was.ch wrote: > Full_Name: Dominik Fässler > Version: 2.4.23 > OS: FreeBSD (8.1-RELEASE) > URL: > Submission from: (NULL) (62.2.101.221) > > > We know that for the moment only BDB versions 4.4 - 4.8 are supported as backend > for SLAPD. > We would be happy, if you could include support for BDB versions 5.x as well. > (For now we are using 5.1) > Thanx. > Added to configure script in HEAD. -- -- 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#6700) memberOf overlay does not handle MODRDN correctly
by raphael.ouazana＠linagora.com 10 Nov '10

10 Nov '10

Full_Name: Raphael Ouazana Version: 2.4.23 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (213.41.232.151) Hi, When using memberOf overlay, a MODRDN request on a member does not update correctly the matching group, even if the memberof-refint option is set to true. In my little understanding, memberof_value_modify calls op->o_bd->be_modify which calls back the overlay code, and finally never reach the backend. Regards, Raphaël Ouazana.

1 0

RE: (ITS#6683) DDS fails with expired branches
by Petteri.Stenius＠ubisecure.com 10 Nov '10

10 Nov '10

Hi, Thank you for your reply. My knowledge about the bdb internals is limited. I have reproduced this issue and reduced it to a small amount of data (see below). I think I have done everything right with regards to setting up and preparing the database and indexes. I've used both ldapmodify and slapadd/slapindex to prepare the db. If you think my indexes are corrupt then can you please give me pointers how to verify? I don't think there exist test cases for operators LE "<=3D" or GE = ">=3D" in the source codes. Thanks, Petteri -----Original Message----- From: Howard Chu [mailto:hyc@symas.com]=20 Sent: Tuesday, November 09, 2010 10:45 AM To: Petteri Stenius Cc: openldap-its(a)openldap.org Subject: Re: (ITS#6683) DDS fails with expired branches Petteri.Stenius(a)ubisecure.com wrote: > Hello, > > Further investigation shows this issue is caused by operator LE search > failing with indexed attributes. Also this indexed search issue is NOT > limited to DDS.=3D20 > > I have reproduced the issue with integerOrderingMatch and > generalizedTimeOrderingMatch.=3D20 > > The piece of code I find suspicious is in servers/back-bdb/idl.c, > somewhere in the middle it reads > > /* skip presence key on range inequality lookups */ > while (rc =3D3D=3D3D 0&& kptr->size !=3D3D len) { > rc =3D3D cursor->c_get( cursor, kptr,&data, flags | > DB_NEXT_NODUP ); > } > > If I remove this block then LE search works as expected with indexed > attributes. The key here seems to be the DB_NEXT_NODUP flag. This flag > causes the iterator block a few lines below to return partial matches. That implies that there's something else corrupt in the index, because the=20 presence key will never be the same size as an equality key. > > Thanks, > Petteri > > -----Original Message----- > From: openldap-bugs-bounces(a)OpenLDAP.org > [mailto:openldap-bugs-bounces@OpenLDAP.org] On Behalf Of > petteri.stenius(a)ubisecure.com > Sent: Monday, October 25, 2010 1:35 PM > To: openldap-its(a)openldap.org > Subject: (ITS#6683) DDS fails with expired branches > > Full_Name:=3D20 > Version: 2.4.23 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.197.205.34) > > > Hello, > > I have a directory with branches of dynamicObject entries. It looks like > if the > entryExpireTimestamp value is the same on objects within a branch then > DDS > search for expired objects will only find the top-most object. This > results in > remove failing with message > > DDS dn=3D3D"cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest" is non-leaf; = deferring. > > > To reproduce > > OpenLDAP 2.4.23, Berkeley DB 4.6.21 > > Use slapadd to prepare directory with following > > dn: cn=3D3DRoot,dc=3D3Dtest > objectClass: top > objectClass: applicationProcess > cn: Root > > dn: cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: top > > dn: cn=3D3Dleaf1,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf1 > > dn: cn=3D3Dleaf2,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf2 > > dn: cn=3D3Dleaf3,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf3 > > > Relevant slapd.conf entries > > database bdb > suffix "cn=3D3DRoot,dc=3D3Dtest" > rootdn "cn=3D3DRoot,dc=3D3Dtest" > rootpw "password" > > overlay dds > dds-default-ttl 3600 > dds-min-ttl 60 > dds-interval 60 > dds-state true > index entryExpireTimestamp eq,pres > > access to dn.subtree=3D3D"cn=3D3DRoot,dc=3D3Dtest" > by users write > by * read > > > Running "slapd -d 1 -d 256" produces following > > put_filter: > "(&(objectClass=3D3DdynamicObject)(entryExpireTimestamp<=3D3D201010250824= 46Z )=3D > )" > put_filter: AND > put_filter_list > "(objectClass=3D3DdynamicObject)(entryExpireTimestamp<=3D3D20101025082446= Z)" > put_filter: "(objectClass=3D3DdynamicObject)" > put_filter: simple > put_simple_filter: "objectClass=3D3DdynamicObject" > put_filter: "(entryExpireTimestamp<=3D3D20101025082446Z)" > put_filter: simple > put_simple_filter: "entryExpireTimestamp<=3D3D20101025082446Z" > ber_scanf fmt ({mm}) ber: > ber_scanf fmt ({mm}) ber: > =3D3D> bdb_search > bdb_dn2entry("cn=3D3Droot,dc=3D3Dtest") > =3D3D> bdb_dn2id("cn=3D3Droot,dc=3D3Dtest") > <=3D3D bdb_dn2id: got id=3D3D0x1 > entry_decode: "cn=3D3DRoot,dc=3D3Dtest" > <=3D3D entry_decode(cn=3D3DRoot,dc=3D3Dtest) > search_candidates: base=3D3D"cn=3D3Droot,dc=3D3Dtest" (0x00000001) = scope=3D3D2 > =3D3D> bdb_dn2idl("cn=3D3Droot,dc=3D3Dtest") > =3D3D> bdb_equality_candidates (objectClass) > =3D3D> key_read > <=3D3D bdb_index_read: failed (-30989) > <=3D3D bdb_equality_candidates: id=3D3D0, first=3D3D0, last=3D3D0 > =3D3D> bdb_equality_candidates (objectClass) > =3D3D> key_read > <=3D3D bdb_index_read 4 candidates > <=3D3D bdb_equality_candidates: id=3D3D4, first=3D3D2, last=3D3D5 > =3D3D> bdb_inequality_candidates (entryExpireTimestamp) > =3D3D> key_read > <=3D3D bdb_index_read 1 candidates > =3D3D> key_read > <=3D3D bdb_index_read: failed (-30989) > <=3D3D bdb_inequality_candidates: id=3D3D1, first=3D3D2, last=3D3D2 > bdb_search_candidates: id=3D3D1 first=3D3D2 last=3D3D2 > entry_decode: "cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest" > <=3D3D entry_decode(cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest) > =3D3D> bdb_dn2id("cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest") > <=3D3D bdb_dn2id: got id=3D3D0x2 > send_ldap_result: conn=3D3D-1 op=3D3D0 p=3D3D0 > bdb_dn2entry("cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest") > =3D3D> bdb_dn2id_children("cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest") > <=3D3D bdb_dn2id_children("cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest"): (0) > send_ldap_result: conn=3D3D-1 op=3D3D0 p=3D3D0 > DDS dn=3D3D"cn=3D3Dtop,cn=3D3Droot,dc=3D3Dtest" is non-leaf; = deferring. > DDS expired=3D3D0 > > > ldapsearch "(entryExpireTimestamp=3D3D*)" produces > > dn: cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3D3Dleaf1,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3D3Dleaf2,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3D3Dleaf3,cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > entryExpireTimestamp: 20101024113626Z > > > where ldapsearch "(entryExpireTimestamp<=3D3D20101024113626Z)" only finds > > dn: cn=3D3Dtop,cn=3D3DRoot,dc=3D3Dtest > entryExpireTimestamp: 20101024113626Z > > > If I change all timestamps to distinct values then expiration of > complete > branches works as expected. > > > Thanks, > Petteri > > > --=20 -- 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#6698) Please add BDB 5.x support for SLAPD
by faessler＠was.ch 10 Nov '10

10 Nov '10

Full_Name: Dominik Fässler Version: 2.4.23 OS: FreeBSD (8.1-RELEASE) URL: Submission from: (NULL) (62.2.101.221) We know that for the moment only BDB versions 4.4 - 4.8 are supported as backend for SLAPD. We would be happy, if you could include support for BDB versions 5.x as well. (For now we are using 5.1) Thanx.

1 0

Re: (ITS#6696) back-sql and pagedResultsControl can be extremely heavy due to no LIMIT
by masarati＠aero.polimi.it 10 Nov '10

10 Nov '10

Howard Chu wrote: >> Using back-sql on large databases along with pagedResult control is not >> advisable. Limiting the number of entries returned by each query is not >> viable as well, since some entries might not mathc the LDAP filter, or >> ACLs or so, possibly leading to less than pageSize entries returned >> within one page. PagedResults could be removed from back-sql, and dealt >> with by an overlay that simply pages results returned by back-sql in a >> single internal search; probably this is the preferable approach, since >> it would also result in a reduction of the complexity of back-sql. >> However, I have little interest in improving back-sql, so patches are >> welcome, as usual... > > The sssvlv overlay already intercepts pagedResults requests if they > occur in combination with the Sort control. It would be trivial to > extend it to always intercept pagedResults, and then we can rip the > paging support out of each of the backends. (Of course, there's a > marginal efficiency advantage to letting back-bdb/hdb do its own paging. > A configurable option might be best.) That's more or less what I had in mind. I assume you merged the two functionalities in one overlay because pagedResult needs special care when combined with SSSVLV, and this might be true for other functionalities, though (e.g. having efficient pagedResult; life would be much better without it, since clients do not need it while it makes servers' life harder). With respect to conditionally exploiting native pagedResult capabilities of back-bdb/hdb I only fear some issues related to glued databases. Those could be possibly solved by disabling native back-bdb/hdb pagedResult handling when used in glued databases, or even more granularly, when a search spans more than one database in a glued configuration, delegating the handling to the overlay in those cases. p.

1 0

Re: (ITS#6696) back-sql and pagedResultsControl can be extremely heavy due to no LIMIT
by hyc＠symas.com 10 Nov '10

10 Nov '10

masarati(a)aero.polimi.it wrote: > Andrew.Gray(a)unlv.edu wrote: >> Full_Name: Andrew Gray >> Version: 2.4.17 >> OS: Debian 5.0 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (131.216.14.1) >> >> >> On receiving LDAP queries with a pagedResultsControl (in this case with a size >> of 250), back-sql generates an extremely inefficient query for every iteration >> in the form of: >> >> SELECT DISTINCT ldap_entries.id,people.local_id,text('UNLVexpperson') AS >> objectClass,ldap_entries.dn AS dn FROM ldap_entries,people,ldap_entry_objclasses >> WHERE people.local_ >> id=ldap_entries.keyval AND ldap_entries.oc_map_id=1 AND upper(ldap_entries.dn) >> LIKE upper('%'||'%OU=PEOPLE,DC=UNLV,DC=EDU') AND ldap_entries.id>250 AND (2=2 OR >> (ldap_entries.id=ldap_entry_objclasses.entry_id AND ldap_entry_objclasses.oc_ >> name='UNLVexpperson')) >> >> (this repeats for id>250, id>500, id>750, etc. etc.) >> >> Ideally (IMO) there really should be a SQL LIMIT applied here, as in this case >> slapd gets back a few tens of thousands of rows on every iteration, and the >> memory usage explodes and eventually gets killed. > > Using back-sql on large databases along with pagedResult control is not > advisable. Limiting the number of entries returned by each query is not > viable as well, since some entries might not mathc the LDAP filter, or > ACLs or so, possibly leading to less than pageSize entries returned > within one page. PagedResults could be removed from back-sql, and dealt > with by an overlay that simply pages results returned by back-sql in a > single internal search; probably this is the preferable approach, since > it would also result in a reduction of the complexity of back-sql. > However, I have little interest in improving back-sql, so patches are > welcome, as usual... The sssvlv overlay already intercepts pagedResults requests if they occur in combination with the Sort control. It would be trivial to extend it to always intercept pagedResults, and then we can rip the paging support out of each of the backends. (Of course, there's a marginal efficiency advantage to letting back-bdb/hdb do its own paging. A configurable option might be best.) -- -- 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#6641) Syncrepl failure with 'overlay unique'
by ondrej.kuznik＠acision.com 09 Nov '10

09 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/07/2010 03:26 PM, andrew.findlay(a)skills-1st.co.uk wrote: > On Tue, Sep 07, 2010 at 05:09:07AM -0700, Howard Chu wrote: > >>> We've talked about doing this isolation in the first refresh upon slapd >>> startup. That might still be a good idea. > > It would certainly help to keep the apparent promises made by things > like the uniqueness overlay. Alternatively you could take the view > that the data will converge eventually and that is all that the LDAP > standards promise. We've hit a similar problem and decided to go this way, i.e. allowing the replication to bypass the uniqueness constraints. In RFC 4533, there are only two claims regarding DIT consistency: <quote> 1.2 Intended Usage Upon completion of each synchronization stage of the operation, all information to construct a synchronized client copy of the content has been provided to the client [...]. Except for transient inconsistencies due to concurrent operation (or other) processing at the server, the client copy is an accurate reflection of the content held by the server. Transient inconsistencies will be resolved by subsequent synchronization operations. [...] This protocol is not intended to be used in applications requiring transactional data consistency. </quote> There is no claim that the DIT should stay consistent wrt. any structural restrictions during one synchronization operation. It might be worth noting that trying to replicate the data through as one transaction, like Andrew suggested (quoted below), would still have been impossible without a change in the overlay to allow it to pass through. >>> Doing it on every refresh seems far more problematic, because without some >>> type of multi-version concurrency control, that means making the server >>> non-responsive until the refresh completes. > > That may not be a problem with refresh-and-persist, as in normal > circumstances I would expect updates to arrive at the consumer in the > same order they hit the supplier (so this bug could not trigger). More > difficult for scheduled refresh mode though. Could the consumer server > simply write-lock every entry involved in the refresh while it processes > the list, and then commit the whole lot in one DB transaction? > > Andrew I have put a preliminary version of patches that modify the unique overlay here ftp://ftp.openldap.org/incoming/ondrej-kuznik-20101109-unique_bypass_v1.tgz They add a new configuration attribute olcUniqueAllowManageBypass (it is prohibitively long for a name, though) that, if set to TRUE, triggers the uniqueness checks not to be performed if the operation has manage privilegies on the entry. There are three separate patches, configuration code regarding the new attribute, the checks in unique_{add,modify,modrdn} and manpage modifications. Some things that should be sorted out before this is complete from my point of view: 1. While there might be a way to find out whether an operation comes from replication or is really issued by a rootdn, I have not found any. As a workaround, I used the "manage" privilege to the entry as a trigger, since this privilege already allows to change the structural objectclass of an entry, operation otherwise prohibited by RFC 4512. 2. When performing a modifyDN operation, the privilege is checked against the entry to be changed instead of the new entry. I found this approach more appropriate than modifying the entry returned by overlay_entry_get_ov as I do not yet understand the implications of doing that and do not know whether it is possible and ok to create a phony entry by hand just for the call to access_allowed. This is clearly marked as a "FIXME" comment in the patch. 3. The entry attribute used for acl checking might be too broad. However, deriving the attributes needed for each domain seemed too complex. At least when this is the first version of a patch for which I have no indication whether even the general idea is considered worth pursuing. 4. The code is similar in all three cases so the first attempt was to move it into unique_search, but there is not enough information available there and would have to be provided by each of the three functions anyway. Howard and/or others, do you consider this solution valid for this ITS? If yes, could you help me address the things that should be sorted out? Last, but not least, the IPR stuff: The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2010 Acision Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License. Regards, Ondrej Kuznik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzZX1QACgkQ9GWxeeH+cXuS6gCdEL7txhDF6ukM3jGAcdZNXuQo lkYAoJXgT8T67OAkETtvYsBuehTV2gO5 =t7jk -----END PGP SIGNATURE----- This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

1 0

Re: (ITS#6696) back-sql and pagedResultsControl can be extremely heavy due to no LIMIT
by masarati＠aero.polimi.it 09 Nov '10

09 Nov '10

Andrew.Gray(a)unlv.edu wrote: > Full_Name: Andrew Gray > Version: 2.4.17 > OS: Debian 5.0 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (131.216.14.1) > > > On receiving LDAP queries with a pagedResultsControl (in this case with a size > of 250), back-sql generates an extremely inefficient query for every iteration > in the form of: > > SELECT DISTINCT ldap_entries.id,people.local_id,text('UNLVexpperson') AS > objectClass,ldap_entries.dn AS dn FROM ldap_entries,people,ldap_entry_objclasses > WHERE people.local_ > id=ldap_entries.keyval AND ldap_entries.oc_map_id=1 AND upper(ldap_entries.dn) > LIKE upper('%'||'%OU=PEOPLE,DC=UNLV,DC=EDU') AND ldap_entries.id>250 AND (2=2 OR > (ldap_entries.id=ldap_entry_objclasses.entry_id AND ldap_entry_objclasses.oc_ > name='UNLVexpperson')) > > (this repeats for id>250, id>500, id>750, etc. etc.) > > Ideally (IMO) there really should be a SQL LIMIT applied here, as in this case > slapd gets back a few tens of thousands of rows on every iteration, and the > memory usage explodes and eventually gets killed. Using back-sql on large databases along with pagedResult control is not advisable. Limiting the number of entries returned by each query is not viable as well, since some entries might not mathc the LDAP filter, or ACLs or so, possibly leading to less than pageSize entries returned within one page. PagedResults could be removed from back-sql, and dealt with by an overlay that simply pages results returned by back-sql in a single internal search; probably this is the preferable approach, since it would also result in a reduction of the complexity of back-sql. However, I have little interest in improving back-sql, so patches are welcome, as usual... p.

1 0

Re: (ITS#6697) Could OpenLdap automatically generate SSHA Hashed userPassword?
by masarati＠aero.polimi.it 09 Nov '10

09 Nov '10

changhong_sun(a)yahoo.cn wrote: > Full_Name: Chang Hong Sun > Version: 2.4.23 > OS: SuSe Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (220.248.0.145) > > > Hi All, > > I've installed OpenLdap 2.4.23 in SUSE Linux, and find that: > 1) The OpenLdap supports the SSHA Hash Algorithm by default: could import or > accept the creation of the Users with the {SSHA}/{SHA} Hashed userPassword. > 2) The OpenLdap provides a command "slappasswd" to generate the hashed password, > while it seems that it is not able to generate the password by the OpenLdap > server automatically: after I created a user without Hashed userPassword, I > checked the data and found that the password keep unchanged and hasn't been > Hashed. > > My question is: > Is it possible to make some configuration, so that the OpenLdap server could > automatically transfer the userPassword to Hashed format? Please direct software usage questions to openldap-technical(a)openldap.org; the ITS is intended to track software bugs. This ITS will be closed. p.

1 0

(ITS#6697) Could OpenLdap automatically generate SSHA Hashed userPassword?
by changhong_sun＠yahoo.cn 09 Nov '10

09 Nov '10

Full_Name: Chang Hong Sun Version: 2.4.23 OS: SuSe Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (220.248.0.145) Hi All, I've installed OpenLdap 2.4.23 in SUSE Linux, and find that: 1) The OpenLdap supports the SSHA Hash Algorithm by default: could import or accept the creation of the Users with the {SSHA}/{SHA} Hashed userPassword. 2) The OpenLdap provides a command "slappasswd" to generate the hashed password, while it seems that it is not able to generate the password by the OpenLdap server automatically: after I created a user without Hashed userPassword, I checked the data and found that the password keep unchanged and hasn't been Hashed. My question is: Is it possible to make some configuration, so that the OpenLdap server could automatically transfer the userPassword to Hashed format? Thanks and Best Regards, Sun Chang Hong

1 0

Re: (ITS#6683) DDS fails with expired branches
by hyc＠symas.com 09 Nov '10

09 Nov '10

Petteri.Stenius(a)ubisecure.com wrote: > Hello, > > Further investigation shows this issue is caused by operator LE search > failing with indexed attributes. Also this indexed search issue is NOT > limited to DDS.=20 > > I have reproduced the issue with integerOrderingMatch and > generalizedTimeOrderingMatch.=20 > > The piece of code I find suspicious is in servers/back-bdb/idl.c, > somewhere in the middle it reads > > /* skip presence key on range inequality lookups */ > while (rc =3D=3D 0&& kptr->size !=3D len) { > rc =3D cursor->c_get( cursor, kptr,&data, flags | > DB_NEXT_NODUP ); > } > > If I remove this block then LE search works as expected with indexed > attributes. The key here seems to be the DB_NEXT_NODUP flag. This flag > causes the iterator block a few lines below to return partial matches. That implies that there's something else corrupt in the index, because the presence key will never be the same size as an equality key. > > Thanks, > Petteri > > -----Original Message----- > From: openldap-bugs-bounces(a)OpenLDAP.org > [mailto:openldap-bugs-bounces@OpenLDAP.org] On Behalf Of > petteri.stenius(a)ubisecure.com > Sent: Monday, October 25, 2010 1:35 PM > To: openldap-its(a)openldap.org > Subject: (ITS#6683) DDS fails with expired branches > > Full_Name:=20 > Version: 2.4.23 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.197.205.34) > > > Hello, > > I have a directory with branches of dynamicObject entries. It looks like > if the > entryExpireTimestamp value is the same on objects within a branch then > DDS > search for expired objects will only find the top-most object. This > results in > remove failing with message > > DDS dn=3D"cn=3Dtop,cn=3Droot,dc=3Dtest" is non-leaf; deferring. > > > To reproduce > > OpenLDAP 2.4.23, Berkeley DB 4.6.21 > > Use slapadd to prepare directory with following > > dn: cn=3DRoot,dc=3Dtest > objectClass: top > objectClass: applicationProcess > cn: Root > > dn: cn=3Dtop,cn=3DRoot,dc=3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: top > > dn: cn=3Dleaf1,cn=3Dtop,cn=3DRoot,dc=3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf1 > > dn: cn=3Dleaf2,cn=3Dtop,cn=3DRoot,dc=3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf2 > > dn: cn=3Dleaf3,cn=3Dtop,cn=3DRoot,dc=3Dtest > objectClass: top > objectClass: device > objectClass: dynamicObject > entryTTL: 60 > entryExpireTimestamp: 20101024113626Z > cn: leaf3 > > > Relevant slapd.conf entries > > database bdb > suffix "cn=3DRoot,dc=3Dtest" > rootdn "cn=3DRoot,dc=3Dtest" > rootpw "password" > > overlay dds > dds-default-ttl 3600 > dds-min-ttl 60 > dds-interval 60 > dds-state true > index entryExpireTimestamp eq,pres > > access to dn.subtree=3D"cn=3DRoot,dc=3Dtest" > by users write > by * read > > > Running "slapd -d 1 -d 256" produces following > > put_filter: > "(&(objectClass=3DdynamicObject)(entryExpireTimestamp<=3D20101025082446Z)= > )" > put_filter: AND > put_filter_list > "(objectClass=3DdynamicObject)(entryExpireTimestamp<=3D20101025082446Z)" > put_filter: "(objectClass=3DdynamicObject)" > put_filter: simple > put_simple_filter: "objectClass=3DdynamicObject" > put_filter: "(entryExpireTimestamp<=3D20101025082446Z)" > put_filter: simple > put_simple_filter: "entryExpireTimestamp<=3D20101025082446Z" > ber_scanf fmt ({mm}) ber: > ber_scanf fmt ({mm}) ber: > =3D> bdb_search > bdb_dn2entry("cn=3Droot,dc=3Dtest") > =3D> bdb_dn2id("cn=3Droot,dc=3Dtest") > <=3D bdb_dn2id: got id=3D0x1 > entry_decode: "cn=3DRoot,dc=3Dtest" > <=3D entry_decode(cn=3DRoot,dc=3Dtest) > search_candidates: base=3D"cn=3Droot,dc=3Dtest" (0x00000001) scope=3D2 > =3D> bdb_dn2idl("cn=3Droot,dc=3Dtest") > =3D> bdb_equality_candidates (objectClass) > =3D> key_read > <=3D bdb_index_read: failed (-30989) > <=3D bdb_equality_candidates: id=3D0, first=3D0, last=3D0 > =3D> bdb_equality_candidates (objectClass) > =3D> key_read > <=3D bdb_index_read 4 candidates > <=3D bdb_equality_candidates: id=3D4, first=3D2, last=3D5 > =3D> bdb_inequality_candidates (entryExpireTimestamp) > =3D> key_read > <=3D bdb_index_read 1 candidates > =3D> key_read > <=3D bdb_index_read: failed (-30989) > <=3D bdb_inequality_candidates: id=3D1, first=3D2, last=3D2 > bdb_search_candidates: id=3D1 first=3D2 last=3D2 > entry_decode: "cn=3Dtop,cn=3DRoot,dc=3Dtest" > <=3D entry_decode(cn=3Dtop,cn=3DRoot,dc=3Dtest) > =3D> bdb_dn2id("cn=3Dtop,cn=3Droot,dc=3Dtest") > <=3D bdb_dn2id: got id=3D0x2 > send_ldap_result: conn=3D-1 op=3D0 p=3D0 > bdb_dn2entry("cn=3Dtop,cn=3Droot,dc=3Dtest") > =3D> bdb_dn2id_children("cn=3Dtop,cn=3Droot,dc=3Dtest") > <=3D bdb_dn2id_children("cn=3Dtop,cn=3Droot,dc=3Dtest"): (0) > send_ldap_result: conn=3D-1 op=3D0 p=3D0 > DDS dn=3D"cn=3Dtop,cn=3Droot,dc=3Dtest" is non-leaf; deferring. > DDS expired=3D0 > > > ldapsearch "(entryExpireTimestamp=3D*)" produces > > dn: cn=3Dtop,cn=3DRoot,dc=3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3Dleaf1,cn=3Dtop,cn=3DRoot,dc=3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3Dleaf2,cn=3Dtop,cn=3DRoot,dc=3Dtest > entryExpireTimestamp: 20101024113626Z > > dn: cn=3Dleaf3,cn=3Dtop,cn=3DRoot,dc=3Dtest > entryExpireTimestamp: 20101024113626Z > > > where ldapsearch "(entryExpireTimestamp<=3D20101024113626Z)" only finds > > dn: cn=3Dtop,cn=3DRoot,dc=3Dtest > entryExpireTimestamp: 20101024113626Z > > > If I change all timestamps to distinct values then expiration of > complete > branches works as expected. > > > Thanks, > Petteri > > > -- -- 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#6683) DDS fails with expired branches
by Petteri.Stenius＠ubisecure.com 09 Nov '10

09 Nov '10

Hello, Further investigation shows this issue is caused by operator LE search failing with indexed attributes. Also this indexed search issue is NOT limited to DDS.=20 I have reproduced the issue with integerOrderingMatch and generalizedTimeOrderingMatch.=20 The piece of code I find suspicious is in servers/back-bdb/idl.c, somewhere in the middle it reads /* skip presence key on range inequality lookups */ while (rc =3D=3D 0 && kptr->size !=3D len) { rc =3D cursor->c_get( cursor, kptr, &data, flags | DB_NEXT_NODUP ); } If I remove this block then LE search works as expected with indexed attributes. The key here seems to be the DB_NEXT_NODUP flag. This flag causes the iterator block a few lines below to return partial matches. Thanks, Petteri -----Original Message----- From: openldap-bugs-bounces(a)OpenLDAP.org [mailto:openldap-bugs-bounces@OpenLDAP.org] On Behalf Of petteri.stenius(a)ubisecure.com Sent: Monday, October 25, 2010 1:35 PM To: openldap-its(a)openldap.org Subject: (ITS#6683) DDS fails with expired branches Full_Name:=20 Version: 2.4.23 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.197.205.34) Hello, I have a directory with branches of dynamicObject entries. It looks like if the entryExpireTimestamp value is the same on objects within a branch then DDS search for expired objects will only find the top-most object. This results in remove failing with message DDS dn=3D"cn=3Dtop,cn=3Droot,dc=3Dtest" is non-leaf; deferring. To reproduce OpenLDAP 2.4.23, Berkeley DB 4.6.21 Use slapadd to prepare directory with following dn: cn=3DRoot,dc=3Dtest objectClass: top objectClass: applicationProcess cn: Root dn: cn=3Dtop,cn=3DRoot,dc=3Dtest objectClass: top objectClass: device objectClass: dynamicObject entryTTL: 60 entryExpireTimestamp: 20101024113626Z cn: top dn: cn=3Dleaf1,cn=3Dtop,cn=3DRoot,dc=3Dtest objectClass: top objectClass: device objectClass: dynamicObject entryTTL: 60 entryExpireTimestamp: 20101024113626Z cn: leaf1 dn: cn=3Dleaf2,cn=3Dtop,cn=3DRoot,dc=3Dtest objectClass: top objectClass: device objectClass: dynamicObject entryTTL: 60 entryExpireTimestamp: 20101024113626Z cn: leaf2 dn: cn=3Dleaf3,cn=3Dtop,cn=3DRoot,dc=3Dtest objectClass: top objectClass: device objectClass: dynamicObject entryTTL: 60 entryExpireTimestamp: 20101024113626Z cn: leaf3 Relevant slapd.conf entries database bdb suffix "cn=3DRoot,dc=3Dtest" rootdn "cn=3DRoot,dc=3Dtest" rootpw "password" overlay dds dds-default-ttl 3600 dds-min-ttl 60 dds-interval 60 dds-state true index entryExpireTimestamp eq,pres access to dn.subtree=3D"cn=3DRoot,dc=3Dtest" by users write by * read Running "slapd -d 1 -d 256" produces following put_filter: "(&(objectClass=3DdynamicObject)(entryExpireTimestamp<=3D20101025082446Z)= )" put_filter: AND put_filter_list "(objectClass=3DdynamicObject)(entryExpireTimestamp<=3D20101025082446Z)" put_filter: "(objectClass=3DdynamicObject)" put_filter: simple put_simple_filter: "objectClass=3DdynamicObject" put_filter: "(entryExpireTimestamp<=3D20101025082446Z)" put_filter: simple put_simple_filter: "entryExpireTimestamp<=3D20101025082446Z" ber_scanf fmt ({mm}) ber: ber_scanf fmt ({mm}) ber: =3D> bdb_search bdb_dn2entry("cn=3Droot,dc=3Dtest") =3D> bdb_dn2id("cn=3Droot,dc=3Dtest") <=3D bdb_dn2id: got id=3D0x1 entry_decode: "cn=3DRoot,dc=3Dtest" <=3D entry_decode(cn=3DRoot,dc=3Dtest) search_candidates: base=3D"cn=3Droot,dc=3Dtest" (0x00000001) scope=3D2 =3D> bdb_dn2idl("cn=3Droot,dc=3Dtest") =3D> bdb_equality_candidates (objectClass) =3D> key_read <=3D bdb_index_read: failed (-30989) <=3D bdb_equality_candidates: id=3D0, first=3D0, last=3D0 =3D> bdb_equality_candidates (objectClass) =3D> key_read <=3D bdb_index_read 4 candidates <=3D bdb_equality_candidates: id=3D4, first=3D2, last=3D5 =3D> bdb_inequality_candidates (entryExpireTimestamp) =3D> key_read <=3D bdb_index_read 1 candidates =3D> key_read <=3D bdb_index_read: failed (-30989) <=3D bdb_inequality_candidates: id=3D1, first=3D2, last=3D2 bdb_search_candidates: id=3D1 first=3D2 last=3D2 entry_decode: "cn=3Dtop,cn=3DRoot,dc=3Dtest" <=3D entry_decode(cn=3Dtop,cn=3DRoot,dc=3Dtest) =3D> bdb_dn2id("cn=3Dtop,cn=3Droot,dc=3Dtest") <=3D bdb_dn2id: got id=3D0x2 send_ldap_result: conn=3D-1 op=3D0 p=3D0 bdb_dn2entry("cn=3Dtop,cn=3Droot,dc=3Dtest") =3D> bdb_dn2id_children("cn=3Dtop,cn=3Droot,dc=3Dtest") <=3D bdb_dn2id_children("cn=3Dtop,cn=3Droot,dc=3Dtest"): (0) send_ldap_result: conn=3D-1 op=3D0 p=3D0 DDS dn=3D"cn=3Dtop,cn=3Droot,dc=3Dtest" is non-leaf; deferring. DDS expired=3D0 ldapsearch "(entryExpireTimestamp=3D*)" produces dn: cn=3Dtop,cn=3DRoot,dc=3Dtest entryExpireTimestamp: 20101024113626Z dn: cn=3Dleaf1,cn=3Dtop,cn=3DRoot,dc=3Dtest entryExpireTimestamp: 20101024113626Z dn: cn=3Dleaf2,cn=3Dtop,cn=3DRoot,dc=3Dtest entryExpireTimestamp: 20101024113626Z dn: cn=3Dleaf3,cn=3Dtop,cn=3DRoot,dc=3Dtest entryExpireTimestamp: 20101024113626Z where ldapsearch "(entryExpireTimestamp<=3D20101024113626Z)" only finds dn: cn=3Dtop,cn=3DRoot,dc=3Dtest entryExpireTimestamp: 20101024113626Z If I change all timestamps to distinct values then expiration of complete branches works as expected. Thanks, Petteri

1 0

Re: (ITS#6693) Value dependent ACL issues
by rhafer＠suse.de 08 Nov '10

08 Nov '10

Hm, that patch was obviously wrong. Even though it resulted in working value-dependent ACLs, it completely broke ACL caching. This patch should work better: ------------------------------------------------------------------- --- a/servers/slapd/slap.h +++ b/servers/slapd/slap.h @@ -1557,6 +1557,7 @@ typedef struct AccessControlState { /* Value dependent acl where processing can restart */ AccessControl *as_vd_acl; + int as_vd_acl_present; int as_vd_acl_count; slap_mask_t as_vd_mask; @@ -1567,7 +1568,7 @@ typedef struct AccessControlState { /* True if started to process frontend ACLs */ int as_fe_done; } AccessControlState; -#define ACL_STATE_INIT { NULL, ACL_NONE, NULL, 0, ACL_PRIV_NONE, -1, 0 } +#define ACL_STATE_INIT { NULL, ACL_NONE, NULL, 0, 0, ACL_PRIV_NONE, -1, 0 } typedef struct AclRegexMatches { int dn_count; --- a/servers/slapd/acl.c +++ b/servers/slapd/acl.c @@ -220,7 +220,7 @@ slap_access_allowed( state = &acl_state; if ( state->as_desc == desc && state->as_access == access && - state->as_vd_acl != NULL ) + state->as_vd_acl_present ) { a = state->as_vd_acl; count = state->as_vd_acl_count; @@ -405,7 +405,7 @@ access_allowed_mask( if ( state->as_desc == desc && state->as_access == access && state->as_result != -1 && - state->as_vd_acl == NULL ) + !state->as_vd_acl_present ) { Debug( LDAP_DEBUG_ACL, "=> access_allowed: result was in cache (%s)\n", @@ -615,7 +615,8 @@ slap_acl_get( continue; } - if ( state->as_vd_acl == NULL ) { + if ( !state->as_vd_acl_present ) { + state->as_vd_acl_present = 1; state->as_vd_acl = prev; state->as_vd_acl_count = *count - 1; ACL_PRIV_ASSIGN ( state->as_vd_mask, *mask ); @@ -714,7 +715,8 @@ slap_acl_get( * Record value-dependent access control state */ #define ACL_RECORD_VALUE_STATE do { \ - if( state && state->as_vd_acl == NULL ) { \ + if( state && !state->as_vd_acl_present ) { \ + state->as_vd_acl_present = 1; \ state->as_vd_acl = a; \ state->as_vd_acl_count = count; \ ACL_PRIV_ASSIGN( state->as_vd_mask, *mask ); \ ------------------------------------------------------------------- Comments welcome. Ralf

1 0

Re: (ITS#6686) VLV overlay fails to handle multiple search operations per LDAP connection
by raphael.ouazana＠linagora.com 05 Nov '10

05 Nov '10

Hi ! Le Ven 29 octobre 2010 11:12, hyc(a)symas.com a écrit : > I guess as long as you observe the svi_max config parameter, there's no > reason > not to adopt your suggestion. Feel free to followup here with your patch > for > review. Here is the patch: ftp://ftp.openldap.org/incoming/raphael-ouazana-101105-sssvlv-multiple-requ… It applies to HEAD of today. If you need it, I can send you a patch for RE24 too. The patch includes the modification of the man page. Legal notice: This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in this following patch were developed by Raphael Ouazana raphael.ouazana(a)linagora.com. These modifications are not subject to any license of Linagora. The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2010 Raphael Ouazana, Linagora Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License. Regards, Raphaël Ouazana

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by david＠dasz.at 05 Nov '10

05 Nov '10

On 11/5/2010 12:03 PM, Howard Chu wrote: > david(a)dasz.at wrote: >> This is a multi-part message in MIME format. >> --------------050908020600020509000208 >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> Content-Transfer-Encoding: 7bit >> >> Hi, >> >> I've tried to rebuild the slapd (from the debian sources) with >> -DSLAP_NO_SL_MALLOC=1, but this build doesn't even manage to finish the >> test-suite which is automatically run. > > You should never build code with this flag. It's for OpenLDAP developers > only, and I personally am deeply opposed to its existence. Its effect on > the code is fundamentally wrong. Dear Howard, does that mean I've wasted a day for nothing? Do you have any better ideas how to debug/fix the original issue? David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg

1 0

ITS#6657
by hyc＠symas.com 05 Nov '10

05 Nov '10

> To: david(a)dasz.at > Cc: openldap-its(a)openldap.org > > Please > > - rebuild with -DSLAP_NO_SL_MALLOC=1 (you only need to recompile sl_malloc.c) This is not helpful. As noted in #6691, the offending allocation is memory residing on the stack. Changing any malloc behavior will have no effect on any stack-based memory use. > - run slapd under valgrind --tool=memcheck --leak-check=full and minimal > loglevel (e.g. -d stats) > > - send valgrind's output (if anything surfaces) > > Thanks, p. > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6657) back-sql segfault in backsql_search
by hyc＠symas.com 05 Nov '10

05 Nov '10

david(a)dasz.at wrote: > This is a multi-part message in MIME format. > --------------050908020600020509000208 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > Hi, > > I've tried to rebuild the slapd (from the debian sources) with > -DSLAP_NO_SL_MALLOC=1, but this build doesn't even manage to finish the > test-suite which is automatically run. You should never build code with this flag. It's for OpenLDAP developers only, and I personally am deeply opposed to its existence. Its effect on the code is fundamentally wrong. -- -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs