- openldap-bugs - openldap.org

Re: (ITS#7689) Configuration directive 'logfile' has no use
by quanah＠zimbra.com 10 Sep '13

10 Sep '13

--On Tuesday, September 10, 2013 4:02 PM +0000 eurban(a)harris.com wrote: > Full_Name: Eric Urban > Version: 2.4.36 > OS: RHEL 6.4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (158.147.58.198) > > > Hi, I have been working on packaging 2.4.36 for RHEL 6.4. No issues > there. One requirement is to have logging enabled by default. OpenLDAP > supports syslog, but its use is discouraged within my business area. I > noticed the 'logfile' configuration directive. I still use the > 'slapd.conf' configuration file format, if that matters. I added the > following line to my 'slapd.conf' "logfile" is not a replacement for syslog logging, and is an entirely separate function. Please read the slapd.conf(5) man page. Closing this ITS as invalid. --Quanah -- Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7689) Configuration directive 'logfile' has no use
by eurban＠harris.com 10 Sep '13

10 Sep '13

Full_Name: Eric Urban Version: 2.4.36 OS: RHEL 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (158.147.58.198) Hi, I have been working on packaging 2.4.36 for RHEL 6.4. No issues there. One requirement is to have logging enabled by default. OpenLDAP supports syslog, but its use is discouraged within my business area. I noticed the 'logfile' configuration directive. I still use the 'slapd.conf' configuration file format, if that matters. I added the following line to my 'slapd.conf' logfile /var/log/openldap/openldap.log loglevel none sync stats Then I did mkdir /var/log/openldap chown ldap:ldap /var/log/openldap I restart OpenLDAP and the log file is created but never written to. If I start openldap with 'slapd -d -1' the log file is written to. I checked in include/ldap_log.h and see that the macros for LogN check against 'ldap_debug' before calling lutil_debug. The pseudo-variable 'ldap_debug' is a preprocessor #define at the bottom of the same file. It is just an integer bitmask for logging. I took a look at servers/slapd/bconfig.c and see that 'config_generic' does an fopen() and then passes the result to lutil_debug_file. So far, so good. In config_loglevel the 'loglevel' directive from my slapd.conf is parsed and assigned to 'ldap_syslog' but never 'ldap_debug'. So slapd in server mode will create this file but never write to it. If you set 'logfile' in slapd.conf and start with the -d flag it will, but this is pretty pointless is as you already have the logging messages in your terminal in that case. Is this intentional? I'm not seeing the utility of the 'logfile' configuration directive. In normal operations it's only purpose will be to create an empty file and to confuse system administrators.

1 0

(ITS#7688) MDB_WRITEMAP + non-writemap process broken
by h.b.furuseth＠usit.uio.no 10 Sep '13

10 Sep '13

Full_Name: Hallvard B Furuseth Version: LMDB_0.9.8 OS: Linux x86_64 URL: Submission from: (NULL) (129.240.203.186) Submitted by: hallvard mdb_env_open(,,MDB_WRITEMAP,) does not grow the data file to the mapsize if another process has it open without MDB_WRITEMAP. The new MDB_env gets Bus Error in mdb_page_alloc() if it tries to grow mt_next_pgno. Broken by 2e7130cab0129e3b72a25d39c5d4e5a5c55cb353 "Allow mdb_env_set_mapsize() on an open environment". It made ftruncate() conditional on 'newsize'. To avoid mapsize wars between environments? Could do: if (flags & MDB_WRITEMAP) { prot |= PROT_WRITE; if (!newsize) { off_t pos = lseek(env->me_fd, 0, SEEK_END); if (pos == (off_t)-1) return ErrCode(); if ((size_t)pos < env->me_mapsize) newsize = 1; } if (newsize && ftruncate(env->me_fd, env->me_mapsize) < 0) return ErrCode(); } But that still has a race between processes mapping the environment at the same time, one process could shrink the map just after another grew it. And I'm unsure how env->me_mapsize would end up in this case. Another way: Move ftruncate() to mdb_page_alloc(), which has no race. Grow to <new mt_next_pgno + 25%>. To avoid seeks, maintain me_txns->mti_next_pgno in mdb_page_alloc{MDB_WRITEMAP} and txn_reset(writer).

1 0

(ITS#7687) slapd with chaining dies on ManageDsaIT control
by ck＠cksoft.de 10 Sep '13

10 Sep '13

Full_Name: Christian Kratzer Version: 2.4.36 OS: CentOS / RedHat Enterprise URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (2003:41:c010:8001:9028:d44e:e3ea:c880) Hi, we have a java application using JNDI that uses the password modify extended operation to change user passwords. This runs fine against our masters but causes an assert when run against our slaves that use chaining to pass the modify request to the masters. slapd: chain.c:199: chaining_control_remove: Assertion `op->o_ctrls != ((void *)0)' failed. Backtrace is as follows: Core was generated by `/usr/local/sbin/slapd -h ldap://:389/ ldaps://:636/ -d 1 -F /usr/local/etc/open'. Program terminated with signal 6, Aborted. #0 0x00007fdf5125c8a5 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install openldap-release-2.4.36-1.el6.x86_64 (gdb) bt #0 0x00007fdf5125c8a5 in raise () from /lib64/libc.so.6 #1 0x00007fdf5125e085 in abort () from /lib64/libc.so.6 #2 0x00007fdf51255a1e in __assert_fail_base () from /lib64/libc.so.6 #3 0x00007fdf51255ae0 in __assert_fail () from /lib64/libc.so.6 #4 0x00007fdf4e7fd3ca in chaining_control_remove (op=0x7fdef81add00, oldctrlsp=0x7fdf07ffe078) at chain.c:199 #5 0x00007fdf4e7feedd in ldap_chain_op (op=0x7fdef81add00, rs=0x7fdf07ffe950, op_f=0x7fdf4e7fc680 <ldap_back_extended>, ref=0x7fdef81ae0c0, depth=0) at chain.c:655 #6 0x00007fdf4e7ffd37 in ldap_chain_response (op=0x7fdef81add00, rs=0x7fdf07ffe950) at chain.c:1092 #7 0x00000000004954d8 in ?? () #8 0x000000000043d2ee in ?? () #9 0x000000000043de49 in ?? () #10 0x000000000043e5ae in slap_send_ldap_extended () #11 0x000000000045defc in fe_extended () #12 0x00000000004957e7 in overlay_op_walk () #13 0x00000000004961c7 in ?? () #14 0x000000000045e315 in do_extended () #15 0x000000000042df79 in ?? () #16 0x000000000042e755 in ?? () #17 0x00007fdf52a6d498 in ldap_int_thread_pool_wrapper (xpool=0x13f1450) at tpool.c:688 #18 0x00007fdf515c4851 in start_thread () from /lib64/libpthread.so.0 #19 0x00007fdf5131290d in clone () from /lib64/libc.so.6 (gdb) When running slapd with heavy logging we save the only difference to ldappasswd which works fine against our masters is that JNDI sets the ManageDsaIT by default. We were subsequently able to work around the issue by changing the default JNDI behaviour so as not to set the ManageDSA IT control with: env.put(Context.REFERRAL, "throw"); As detailed in following related post and jndi documentation: http://www.openldap.org/lists/ietf-ldapext/200409/msg00035.html http://docs.oracle.com/javase/1.4.2/docs/guide/jndi/jndi-ldap-gl.html#refer… It would of course be helpfull if slapd would handle the situation slightly more gracefully. Even though the control is utterly useless in our case with chaining it is the default on jndi so handling this case would be helpfull to all java users out there. I am not quire sure where this goes wrong exactly. If anybody can write up a patch I would be more than gratefull to test as we have a reproducible test setup on hand in our lab that we can run any time. I can also retest with fuller debug symbols than above if required. Seems only our modules hat debuginfo at the time of the backtrace. Greetings Christian Kratzer CK Software GmbH

1 0

Re: (ITS#7398) Retrieve LDAP server cert
by hyc＠symas.com 10 Sep '13

10 Sep '13

Michael Ströder wrote: > On Fri, 21 Sep 2012 10:43:42 -0700 Howard Chu <hyc(a)symas.com> wrote >> michael(a)stroeder.com wrote: >>> Feature request: >>> When using LDAPS or StartTLS it would be sometimes handy to retrieve the >>> LDAP server certificate over the LDAP client API. >>> >>> Opinions? >> >> And then what? I think it'd be straightforward for us to return a copy of it >> in DER binary format. What do clients need to do with it? > > In my case (web2ldap): Simply display it to the user. Probably would have been easier to just return the signature. > If it's not too much work this would be a handy feature. Added in master, please test - I have not tested any of this. -- -- 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#7686) Feature request: TLS prot/cipher retrievable with ldap_get_option()
by hyc＠symas.com 09 Sep '13

09 Sep '13

michael(a)stroeder.com wrote: > Full_Name: > Version: > OS: > URL: > Submission from: (NULL) (79.227.140.201) > > > Similar to logging at server-side (see ITS#7683) it should be possible for a > LDAP client to retrieve the TLS protocol version and cipher suites actually > negotiated by call to ldap_get_option(3) to be able to make decisions according > to local security policy. > > Added in master, tho I logged it against ITS#7683. -- -- 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#7686) Feature request: TLS prot/cipher retrievable with ldap_get_option()
by michael＠stroeder.com 09 Sep '13

09 Sep '13

Full_Name: Version: OS: URL: Submission from: (NULL) (79.227.140.201) Similar to logging at server-side (see ITS#7683) it should be possible for a LDAP client to retrieve the TLS protocol version and cipher suites actually negotiated by call to ldap_get_option(3) to be able to make decisions according to local security policy.

1 0

Re: (ITS#7381) Dynamically added chaining configuration stops working after restart
by hyc＠symas.com 09 Sep '13

09 Sep '13

Ivan Nejgebauer wrote: > On 06.09.2013. 21:56, hyc(a)symas.com wrote: >> ian(a)uns.ac.rs wrote: >>> If a minimal chaining configuration is dynamically added to a consumer server in >>> a provider/consumer pair running delta-syncrepl, it will stop working when the >>> consumer is restarted. The configuration is modelled after the one used in >>> test022 in the OpenLDAP source distribution: >> >> Sorry this report was neglected for so long, and thanks for the excellent test >> case. This is now fixed in git master. > > Tested against git master (721e46fe6695077d63a3df6ea2e397920a72308d) with the original > use case and it works, thanks. However, slapd now segfaults if started with cn=config > obtained by converting an existing chaining configuration from slapd.conf. Steps to > reproduce, using the scripts from the archive attached to the original report: Ah thanks. Previous commit changed too much. Fixed now in master. > $ make clean-all replica-chaining > $ ./start-replica.sh # segfault > > The crash is in chain_ldadd, and occurs because the first back-ldap instance in the > converted configuration lacks an olcDbURI. I have attached a patch which inserts a > dummy URI in the common parameter structure when it's allocated. This URI > (ldap://0.0.0.0) should never match any actual referral, so the instance can only > serve to initialize common parameters (which happens with the first instance anyway, > if I understood the code correctly.) > -- -- 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#7381) Dynamically added chaining configuration stops working after restart
by ian＠uns.ac.rs 09 Sep '13

09 Sep '13

This is a multi-part message in MIME format. --------------070406020601050207030907 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 06.09.2013. 21:56, hyc(a)symas.com wrote: > ian(a)uns.ac.rs wrote: >> If a minimal chaining configuration is dynamically added to a consumer server in >> a provider/consumer pair running delta-syncrepl, it will stop working when the >> consumer is restarted. The configuration is modelled after the one used in >> test022 in the OpenLDAP source distribution: > > Sorry this report was neglected for so long, and thanks for the excellent test > case. This is now fixed in git master. Tested against git master (721e46fe6695077d63a3df6ea2e397920a72308d) with the original use case and it works, thanks. However, slapd now segfaults if started with cn=config obtained by converting an existing chaining configuration from slapd.conf. Steps to reproduce, using the scripts from the archive attached to the original report: $ make clean-all replica-chaining $ ./start-replica.sh # segfault The crash is in chain_ldadd, and occurs because the first back-ldap instance in the converted configuration lacks an olcDbURI. I have attached a patch which inserts a dummy URI in the common parameter structure when it's allocated. This URI (ldap://0.0.0.0) should never match any actual referral, so the instance can only serve to initialize common parameters (which happens with the first instance anyway, if I understood the code correctly.) -- Ivan Nejgebauer Glavni sistem inženjer CIT-UNS/ARMUNS Univerzitet u Novom Sadu Trg Dositeja Obradovića 5 21000 Novi Sad +381 21 485 2025 ian(a)uns.ac.rs www.uns.ac.rs --------------070406020601050207030907 Content-Type: text/x-patch; name="0001-Fix-crash-w-converted-chain-config.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0001-Fix-crash-w-converted-chain-config.patch" >From 49dc118a97cc5b7e0723905faf08480facb78912 Mon Sep 17 00:00:00 2001 From: Ivan Nejgebauer <ian(a)uns.ac.rs> Date: Mon, 9 Sep 2013 11:33:02 +0200 Subject: [PATCH] Fix crash w/converted chain config As a result of the fix for ITS#7381 (4d02a43ec9a4be422d83094e8d39b7ef3bc290c5) slapd segfaults if started with dynamic configuration after converting a slapd.conf chaining setup to cn=config. This is because the common back-ldap parameters, emitted as the first olcDatabase entry, lack an olcDbURI attribute. This patch adds a dummy LDAP URI which should never match a real one (ldap://0.0.0.0) to the common parameter structure. --- servers/slapd/back-ldap/chain.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/servers/slapd/back-ldap/chain.c b/servers/slapd/back-ldap/chain.c index a7c53ed..ab71b21 100644 --- a/servers/slapd/back-ldap/chain.c +++ b/servers/slapd/back-ldap/chain.c @@ -2019,6 +2019,7 @@ ldap_chain_db_init_common( BackendInfo *bi = be->bd_info; ldapinfo_t *li; int rc; + char *dummy_uri = "ldap://0.0.0.0"; be->bd_info = lback; be->be_private = NULL; @@ -2029,6 +2030,8 @@ ldap_chain_db_init_common( li = (ldapinfo_t *)be->be_private; li->li_urllist_f = NULL; li->li_urllist_p = NULL; + li->li_uri = ch_strdup( dummy_uri ); + li->li_bvuri = ch_calloc( sizeof( struct berval ), 1 ); be->bd_info = bi; -- 1.8.1.2 --------------070406020601050207030907--

1 0

Re: (ITS#7685) Config directive TLSProtocolMin not converted to attribute olcTLSProtocolMin
by michael＠stroeder.com 08 Sep '13

08 Sep '13

Howard Chu wrote: > michael(a)stroeder.com wrote: >> TLSProtocolMin 3.2 >> >> I'd expect this to appear as attribute 'olcTLSProtocolMin' in cn=config but >> it's >> missing. >> > Fixed in master Seems to work. Thanks. Ciao, Michael.

1 0

Re: (ITS#7678) Operational Error propagated from back-meta
by hyc＠symas.com 07 Sep '13

07 Sep '13

Matt Hamilton wrote: > On 2 Sep 2013, at 04:15 PM, Howard Chu <hyc(a)symas.com> wrote: > >> matth(a)netsight.co.uk wrote: >>> Full_Name: Matt Hamilton >>> Version: 2.4.36 >>> OS: Linux >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (213.133.64.253) >>> >>> >>> I am using the meta backend to query multiple LDAP (AD) backends. This is to >>> consolidate several directories in different departments into one. We attempt >>> both simple binds with username/password and also anon binds to look up user >>> information. >> >> That doesn't make much sense, since AD disallows anonymous Binds. > > Sorry, I wasn't clear. I mean we do both anon and simple binds to OpenLDAP. Hence why the config has credentials in it to use against the backends if not supplied by the client. > >>> At the moment, trying to do an authenticated simple bind to slapd caused an >>> Operational Error to be propagated to the client regardless of the setting of >>> 'onerr'. Even when a result is successfully found. This is due to one server in >>> the backend succeeding and the other returning an operational error due to an >>> invalid bind (as would be expected as the credentials supplied from the client >>> will only work with one of the backends). >>> >>> Looking at servers/slapd/back-meta/search.c at around line 1903 it appears that >>> the code is not checking for 'Operational Error' as a specific case above and so >>> uses the default case (line 1665). Hence sres is set to 'Operational Error' too >>> at line 1934. >> >> back-meta/search.c has nothing to do with Binds. Not sure what you're trying to demonstrate there. > > I'm not talking about binds there. I'm talking about errors being propagated. You said, exactly: >>> At the moment, trying to do an authenticated simple bind to slapd caused an Operational Error to be propagated to the client regardless of the setting of 'onerr'. <<< So again, are you talking about Bind or are you talking about Search? I'm unable to reproduce any of the behavior you're describing since the config snippets you provided reference servers that are private to your network. Nor do I have any local AD servers to test against. Nor have you given exact details of the client side commands being issued. With so little ungarbled information to go on, we cannot investigate. -- -- 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#7669) tool_bind in common.c should be doing conditional assert
by hyc＠symas.com 07 Sep '13

07 Sep '13

k.venkata.kiran(a)ericsson.com wrote: > Full_Name: Venkata Kiran K > Version: 2.4.35 > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (192.71.175.12) > > > tool_bind has below assert which might be hit when nsctrls is not updated > > assert(nsctrls < (int) (sizeof(sctrls) / sizeof(sctrls[0]))); nsctrls is initialized to 0. If it is not updated, the assert condition will of course be true, so the problem you describe cannot arise. Please provide a test case to demonstrate the problem you're seeing, otherwise 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#7683) Feature request: write TLS prot/cipher to syslog
by hyc＠symas.com 07 Sep '13

07 Sep '13

michael(a)stroeder.com wrote: > Full_Name: > Version: HEAD > OS: > URL: > Submission from: (NULL) (79.219.124.115) > > > For debugging which TLS protocol version and cipher suites were actually > negotiated with several LDAP clients this information would be written to the > syslog message. > > Current logging: > > conn=1000 fd=12 TLS established tls_ssf=256 ssf=256 > > Suggestion: > > conn=1000 fd=12 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.1 > tls_cipher=DHE-RSA-AES256-SHA256 > > Added to master. MozNSS version is untested due to absence of PEM support in MozNSS. (See https://bugzilla.mozilla.org/show_bug.cgi?id=402712 - whatever PEM support that may exist is not of usable quality.) -- -- 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#7684) Admin Guide: Correct 'TLSEphemeralDHParamFile' to 'TLSDHParamFile'
by hyc＠symas.com 07 Sep '13

07 Sep '13

michael(a)stroeder.com wrote: > Full_Name: > Version: HEAD > OS: > URL: > Submission from: (NULL) (79.219.124.115) > > > The admin guide incorrectly mentions the configuration directive name > 'TLSEphemeralDHParamFile' instead of 'TLSDHParamFile' like described in > slapd.conf(5). Thanks, fixed in master. (Also partly fixed in ITS#7506) > > See: http://www.openldap.org/doc/admin24/tls.html > > See this trivial patch: > > diff --git a/doc/guide/admin/aspell.en.pws b/doc/guide/admin/aspell.en.pws > index 3683f98..9921963 100644 > --- a/doc/guide/admin/aspell.en.pws > +++ b/doc/guide/admin/aspell.en.pws > @@ -23,7 +23,7 @@ ddd > DAs > TLSCACertificateFile > BNF > -TLSEphemeralDHParamFile > +TLSDHParamFile > ppolicy > gavin > ASN > diff --git a/doc/guide/admin/tls.sdf b/doc/guide/admin/tls.sdf > index 00bf83c..9e3243e 100644 > --- a/doc/guide/admin/tls.sdf > +++ b/doc/guide/admin/tls.sdf > @@ -188,7 +188,7 @@ and it doesn't need very much data to work. > > This directive is ignored with GnuTLS and Mozilla NSS. > > -H4: TLSEphemeralDHParamFile <filename> > +H4: TLSDHParamFile <filename> > > This directive specifies the file that contains parameters for > Diffie-Hellman ephemeral key exchange. This is required in order > > > -- -- 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#7685) Config directive TLSProtocolMin not converted to attribute olcTLSProtocolMin
by hyc＠symas.com 07 Sep '13

07 Sep '13

michael(a)stroeder.com wrote: > Full_Name: > Version: > OS: > URL: > Submission from: (NULL) (79.219.124.115) > > > I have in my static slapd.conf: > > TLSProtocolMin 3.2 > > I'd expect this to appear as attribute 'olcTLSProtocolMin' in cn=config but it's > missing. > > Fixed in master -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7500) libldap starttls crashes if invalid GnuTLS cipher suite string
by hyc＠symas.com 07 Sep '13

07 Sep '13

jouko.orava(a)iki.fi wrote: > 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 is now fixed in git master. > > 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. > > -- -- 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#7434) idassert-bind fails after restarting slapd
by hyc＠symas.com 07 Sep '13

07 Sep '13

blance3459(a)hotmail.com wrote: > Full_Name: Barry Lance > Version: 2.4.28 > OS: Ubuntu 12.04 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (70.226.37.226) It appears the submitter found an alternate solution, but just for future reference this issue was the same as ITS#7381, now fixed in git master. > > Two servers: Master (192.168.1.1) and Replica (192.168.1.2) both running slap > 2.4.28 and ubuntu 12.04. Replica is a replication partner of Master using > syncrepl. Replication is working fine. When I attempt to add a chain overlay > to Replica to send all writes over to the master, it works exactly as expected > allowing both normal users and the rootdn to make appropriate changes. However, > once I either reboot the replica server or restart slapd, the chain overlay > fails to allow any changes on the master. Looking at syslog shows that before > the reboot/restart the requesting users' dn is proxied over as expected. After > the restarting slapd or rebooting Replica, all changes are proxied anonymously > (dn=""). > > I am using simple binds at this point in the project, but it doesn't seems to > matter if I proxy in the clear, ldaps, or TLS the result is the same. All three > methods can successfully negotiate a connection. I've even tried switching > between using the rootdn and a different user as the binddn in my overlay, but > the result is still the same no matter what I use for the binddn. When I look > at my config, I notice that "chain-idassert-bind" appears to be hashed or > encrypted in thew config. Is that normal? Just seems really odd that my config > would work immediately when added, but fail after the the daemon has been > restarted. Am I missing something really silly? Hopefully, someone can assist > me on this. I've been driving myself crazy trying to figure out why this > behavior is occurring. > > Disclaimer: I am using openldap as part of my capstone project for graduation. > I'm not asking for anyone to do my "homework" for me, I'm just stuck on this one > issue that I would love to resolve so I can move on to the Kerberos phase of my > project (and maybe even study for an exam coming up in my algorithms class next > week). > > Here is my overlay config using the rootDN and TLS (on Replica): > > dn: olcDatabase=ldap,olcOverlay={0}chain,olcDatabase={-1}frontend, cn=config > changetype: add > objectClass: olcLDAPConfig > objectClass: olcChainDatabase > olcDatabase: {0}ldap > olcDbURI: "ldap://master.example.net/" > olcDbRebindAsUser: TRUE > olcDbIDAssertBind: bindmethod=simple > binddn="cn=admin,dc=example,dc=net" > credentials=(secret) > mode=self > starttls=critical > tls_cacert=/etc/ssl/certs/cacert.pem > tls_reqcert=demand > > And without TLS (also on Replica): > > dn: olcDatabase=ldap,olcOverlay={0}chain,olcDatabase={-1}frontend, cn=config > changetype: add > objectClass: olcLDAPConfig > objectClass: olcChainDatabase > olcDatabase: {0}ldap > olcDbURI: "ldap://master.example.net/" > olcDbRebindAsUser: TRUE > olcDbIDAssertBind: bindmethod=simple > binddn="cn=admin,dc=example,dc=net" > credentials=(secret) > mode=self > > -- -- 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#7595) OpenLDAP lacks a ECDHE key generation callback
by hyc＠symas.com 07 Sep '13

07 Sep '13

crest(a)tzi.de wrote: > Full_Name: Jan Bramkamp > Version: 2.4.35 > OS: FreeBSD 9.1 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (79.230.127.217) > > > OpenLDAP supports PFS TLS cipher suites using DHE with the > DH *tlso_tmp_dh_cb(SSL*,int,int) callback in libraries/libldap/tls_o.c. > DHE-RSA/DSS cipher suites are very CPU intensive and noticeably increase latency > on low-power hardware. While OpenLDAP supports ECDH-ECDSA cipher suites these > lack the PFS offered by DHE-RSA/DSS cipher suites. > >>From my initial search it looks like the correct API to register such a callback > would be SSL_CTX_set_tmp_ecdh_callback(), but im not familiar the OpenLDAP code > base so patching it my self could have unintended consequences. > > This how the CA was generated: > CURVE=secp384r1 > > openssl ecparam -out private/ca-key.pem -name $CURVE -genkey && > openssl req -new -x509 -days 365 -key private/ca-key.pem -out > certs/ca-cert.pem > > openssl ecparam -out private/auth1-key.pem -name $CURVE -genkey && > openssl req -new -key private/auth1-key.pem -out newcerts/auth1-csr.pem && > openssl ca -config /usr/local/openssl/openssl.cnf -out certs/auth1-cert.pem > -infiles newcerts/auth1-csr.pem > > The (EC)DH paramter file was generated with: > openssl ecparam -name $CURVE > > This was tested with slapd linked against OpenSSL 1.0.1e from ports on FreeBSD > 9.1/amd64. It seems that current events have focused more attention on Perfect Forward Secrecy, now that news about NSA eavesdropping is everywhere. It's worth noting Bruce Schneier's recommendation to avoid Elliptic Curve algorithms, since their design has been heavily influenced by the NSA. http://www.theguardian.com/world/2013/sep/05/nsa-how-to-remain-secure-surve… (Section 5.) -- -- 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#7506) Diffie-Hellman parameters (DHParamFile) are improperly handled
by hyc＠symas.com 07 Sep '13

07 Sep '13

Howard Chu wrote: > ben(a)bjencks.net wrote: >> I suppose I should attach a test case: > > Thanks, patches applied to master (with some tweaks). >> >> cd $WORKDIR >> openssl dhparam 1536 > dh1536.pem >> openssl req -new -newkey rsa:2048 -keyout server.key \ >> -out server.crt -sha256 -nodes -subj '/CN=localhost/' -x509 >> >> For GnuTLS, load the following config: >> dn: cn=config >> objectClass: olcGlobal >> cn: config >> olcTLSCertificateFile: $WORKDIR/server.crt >> olcTLSCertificateKeyFile: $WORKDIR/server.key >> olcTLSCipherSuite: NONE:+VERS-TLS1.1:+VERS-TLS1.0:+AES-128-CBC: >> +DHE-RSA:+SHA1:+COMP-NULL >> olcTLSDHParamFile: $WORKDIR/dh1536.pem >> >> dn: olcDatabase={0}config,cn=config >> objectClass: olcDatabaseConfig >> olcDatabase: {0}config >> >> For Openssl, change olcTLSCipherSuite to: >> olcTLSCipherSuite: aRSA+AES128+kEDH >> >> Start up slapd with the config, listening on ldaps://localhost:6636. >> >> openssl s_client -connect localhost:6636 >> >> With GnuTLS this will fail negotiation; with OpenSSL it will use 1024 >> bit parameters rather than the 1536 bits params we specified. >> >> The only way I've found to find the actual parameter size is to tcpdump >> the negotiation. First, verify that the negotiated cipher suite is >> DHE-RSA-AES128-SHA according to s_client, then: >> >> tcpdump -i lo -wldap.pcap port 6636 >> wireshark ldap.pcap >> Apply the SSL decode to the traffic (right click on packet, Decode As, >> Transport tab, SSL), find the Server Key Exchange packet, select the >> Server Key Exchange portion of the handshake message, and look at the >> hex dump. >> >> It should start with 0c, followed by a three byte size, then the next >> two bytes are the length of the DH parameters: 0080 for 1024 bits, 00c0 >> for 1536 bits. For future reference, you can check this just using openssl s_client -connect localhost:6636 -debug -state SSL_connect:SSLv3 read server certificate A read from 0x16b0c20 [0x16b6cf3] (5 bytes => 5 (0x5)) 0000 - 16 03 02 03 0d ..... read from 0x16b0c20 [0x16b6cf8] (781 bytes => 781 (0x30D)) 0000 - 0c 00 03 09 01 00 a8 e0-4a 3d d1 d2 73 a8 bd 2e ........J=..s... In this case 0c 00 03 09 marks the Server Key Exchange and length, and 01 00 indicates 2048 bits (which matches the dhparams I used). -- -- 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#7506) Diffie-Hellman parameters (DHParamFile) are improperly handled
by hyc＠symas.com 07 Sep '13

07 Sep '13

ben(a)bjencks.net wrote: > I suppose I should attach a test case: Thanks, patches applied to master (with some tweaks). > > cd $WORKDIR > openssl dhparam 1536 > dh1536.pem > openssl req -new -newkey rsa:2048 -keyout server.key \ > -out server.crt -sha256 -nodes -subj '/CN=localhost/' -x509 > > For GnuTLS, load the following config: > dn: cn=config > objectClass: olcGlobal > cn: config > olcTLSCertificateFile: $WORKDIR/server.crt > olcTLSCertificateKeyFile: $WORKDIR/server.key > olcTLSCipherSuite: NONE:+VERS-TLS1.1:+VERS-TLS1.0:+AES-128-CBC: > +DHE-RSA:+SHA1:+COMP-NULL > olcTLSDHParamFile: $WORKDIR/dh1536.pem > > dn: olcDatabase={0}config,cn=config > objectClass: olcDatabaseConfig > olcDatabase: {0}config > > For Openssl, change olcTLSCipherSuite to: > olcTLSCipherSuite: aRSA+AES128+kEDH > > Start up slapd with the config, listening on ldaps://localhost:6636. > > openssl s_client -connect localhost:6636 > > With GnuTLS this will fail negotiation; with OpenSSL it will use 1024 > bit parameters rather than the 1536 bits params we specified. > > The only way I've found to find the actual parameter size is to tcpdump > the negotiation. First, verify that the negotiated cipher suite is > DHE-RSA-AES128-SHA according to s_client, then: > > tcpdump -i lo -wldap.pcap port 6636 > wireshark ldap.pcap > Apply the SSL decode to the traffic (right click on packet, Decode As, > Transport tab, SSL), find the Server Key Exchange packet, select the > Server Key Exchange portion of the handshake message, and look at the > hex dump. > > It should start with 0c, followed by a three byte size, then the next > two bytes are the length of the DH parameters: 0080 for 1024 bits, 00c0 > for 1536 bits. -- -- 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#7685) Config directive TLSProtocolMin not converted to attribute olcTLSProtocolMin
by michael＠stroeder.com 07 Sep '13

07 Sep '13

Full_Name: Version: OS: URL: Submission from: (NULL) (79.219.124.115) I have in my static slapd.conf: TLSProtocolMin 3.2 I'd expect this to appear as attribute 'olcTLSProtocolMin' in cn=config but it's missing.

1 0

(ITS#7684) Admin Guide: Correct 'TLSEphemeralDHParamFile' to 'TLSDHParamFile'
by michael＠stroeder.com 07 Sep '13

07 Sep '13

Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (79.219.124.115) The admin guide incorrectly mentions the configuration directive name 'TLSEphemeralDHParamFile' instead of 'TLSDHParamFile' like described in slapd.conf(5). See: http://www.openldap.org/doc/admin24/tls.html See this trivial patch: diff --git a/doc/guide/admin/aspell.en.pws b/doc/guide/admin/aspell.en.pws index 3683f98..9921963 100644 --- a/doc/guide/admin/aspell.en.pws +++ b/doc/guide/admin/aspell.en.pws @@ -23,7 +23,7 @@ ddd DAs TLSCACertificateFile BNF -TLSEphemeralDHParamFile +TLSDHParamFile ppolicy gavin ASN diff --git a/doc/guide/admin/tls.sdf b/doc/guide/admin/tls.sdf index 00bf83c..9e3243e 100644 --- a/doc/guide/admin/tls.sdf +++ b/doc/guide/admin/tls.sdf @@ -188,7 +188,7 @@ and it doesn't need very much data to work. This directive is ignored with GnuTLS and Mozilla NSS. -H4: TLSEphemeralDHParamFile <filename> +H4: TLSDHParamFile <filename> This directive specifies the file that contains parameters for Diffie-Hellman ephemeral key exchange. This is required in order

1 0

(ITS#7683) Feature request: write TLS prot/cipher to syslog
by michael＠stroeder.com 07 Sep '13

07 Sep '13

Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (79.219.124.115) For debugging which TLS protocol version and cipher suites were actually negotiated with several LDAP clients this information would be written to the syslog message. Current logging: conn=1000 fd=12 TLS established tls_ssf=256 ssf=256 Suggestion: conn=1000 fd=12 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.1 tls_cipher=DHE-RSA-AES256-SHA256

1 0

Re: (ITS#7381) Dynamically added chaining configuration stops working after restart
by hyc＠symas.com 06 Sep '13

06 Sep '13

ian(a)uns.ac.rs wrote: > Full_Name: Ivan Nejgebauer > Version: 2.4.32 > OS: CentOS 5 > URL: ftp://ftp.openldap.org/incoming/ivannejgebauer-120905.tgz > Submission from: (NULL) (2001:4170:2000:2:213:d3ff:fecf:b9ea) > > > If a minimal chaining configuration is dynamically added to a consumer server in > a provider/consumer pair running delta-syncrepl, it will stop working when the > consumer is restarted. The configuration is modelled after the one used in > test022 in the OpenLDAP source distribution: Sorry this report was neglected for so long, and thanks for the excellent test case. This is now fixed in git master. > > dn: olcOverlay={0}chain,olcDatabase={-1}frontend,cn=config > objectClass: olcOverlayConfig > objectClass: olcChainConfig > olcOverlay: {0}chain > > dn: olcDatabase={0}ldap,olcOverlay={0}chain,olcDatabase={-1}frontend,cn=config > objectClass: olcLDAPConfig > objectClass: olcChainDatabase > olcDatabase: {0}ldap > olcDbIDAssertBind: bindmethod=simple binddn="cn=Manager,dc=example,dc=com" > credentials="secret" mode=self > olcDbURI: "ldap://localhost:6389" > > Scripts and data for replicating the issue are in the referenced archive. Quick > summary: > > # make clean-all master replica > # ./start-master.sh > # ./start-replica.sh > # ./replica-apply.sh pmod-add.ldif # returns referral > # ./replica-conf.sh chain.ldif # adds chaining configuration > # ./replica-apply.sh pmod-add.ldif # chains to master > # ./stop-replica.sh > # ./start-replica.sh > # ./replica-apply.sh pmod-del.ldif # returns referral, but shouldn't > > I have tested both 2.4.32 and git master > (54a111907b48900e1ce5de12a9d87818a334423d). > > -- -- 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#7682) LMDB: [PATCH] mdb_env_copy should retry open() if O_DIRECT fails
by hyc＠symas.com 06 Sep '13

06 Sep '13

sog(a)msg.com.mx wrote: > Full_Name: Salvador Ortiz > Version: 24 > OS: Linux > URL: ftp://ftp.msg.com.mx/pub/varios/0001-In-mdb_env_copy-retry-open-if-O_DIRECT-fails.patch > Submission from: (NULL) (187.162.45.111) > > > If the OS defines O_DIRECT mdb_env_copy unconditionally uses it, but according > to open(2): "Some file systems may not implement the flag and open() will > fail with EINVAL if it is used." > > In this cases mdb_env_copy should retry without the flag. > > The attached patch implements that. > > Thanks, applied. -- -- 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