openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

Re: (ITS#6839) Expanded documentation for ldapi: and SASL EXTERNAL
by hyc＠symas.com 18 Feb '11

18 Feb '11

Andrew Findlay wrote: > On Thu, Feb 17, 2011 at 04:21:35PM -0800, Howard Chu wrote: > >>> URL: ftp://ftp.openldap.org/incoming/afindlay-slapi-doc-patch-20110217a > >> This patch fails to apply to HEAD. Please re-read the contributing >> guidelines; all patches must be against HEAD. > > It applies perfectly to the copy of HEAD that I downloaded this > morning: Strange. Must have had some end-of-line issues here. re: TLS Authentication Identity Format Strictly speaking, the order of components is not changed at all. The sequence of RDNs in the DN is what it is; just that the convention for *displaying* it is ass-backwards in LDAP. I'm afraid the wording here will confuse people into thinking that the *semantics* of the DN are changed, when it's only a display issue. > andrew@slab:~/src/openldap-head> cvs -z3 checkout -P -rHEAD openldap > ... much logging deleted ... > andrew@slab:~/src/openldap-head> cd openldap > andrew@slab:~/src/openldap-head/openldap> patch -b -p0< ../afindlay-slapi-doc-patch-20110217a > patching file doc/man/man8/slapd.8 > patching file doc/guide/admin/runningslapd.sdf > patching file doc/guide/admin/sasl.sdf > patching file doc/guide/preamble.sdf > > Andrew -- -- 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#6838) TLS client will not accept certificate for 'localhost'
by Kurt＠OpenLDAP.org 18 Feb '11

18 Feb '11

And, for the OP, I suggest issuing your test certificates for the FQDN = "test" and then setting up name service to resolve this to local host. = Using "test" indicates that the scope of name is limited to some = infrastructure used for testing (and is not a name used on the public = Internet). -- Kurt=

1 0

Re: (ITS#6838) TLS client will not accept certificate for 'localhost'
by Kurt＠OpenLDAP.org 18 Feb '11

18 Feb '11

On Feb 18, 2011, at 9:37 AM, hyc(a)symas.com wrote: > Closing this ITS. It's not a regression and not a bug, just a long = established=20 > feature. Right, the bug is listing non-fully-qualified names as subjects in the = certificate. So, generally speaking, subject names checks fail, as they should fail, = when the asserted name is not fully-qualified. The intent of the code is avoid always failing when the = non-fully-qualified asserted name can be securely transformed into a = fully-qualified name. This is a feature. -- Kurt=

1 0

Re: (ITS#6838) TLS client will not accept certificate for 'localhost'
by hyc＠symas.com 18 Feb '11

18 Feb '11

rhafer(a)suse.de wrote: > Am Freitag 18 Februar 2011, 13:17:17 schrieb > andrew.findlay(a)skills-1st.co.uk: >> On Fri, Feb 18, 2011 at 12:30:25AM +0000, hyc(a)symas.com wrote: >>> Used to work - since when, what release, what else has changed since >>> then? >> >> Unfortunately I cannot tell you exactly when this changed. In any >> case, the change only affects a different bug which was masking the >> problem that I now see. >> >> I do know that 2.3.32 as shipped with SLES 10.3 masks the problem by >> not checking the server certificate properly. So does 2.4.12 as >> shipped with OpenSuSE 11.1. Both will allow ldapsearch -ZZ to connect >> to *any* TLS-capable server if they do *not* have access to the CA >> certificate. >> >> 2.4.24 built on OpenSuSE 11.3 (i.e. using OpenSSL 1.0) correctly >> refuses to connect if there is no CA cert. > Yes, older openSUSE releases used a bad (i.e. less secure) default for > the TLS_REQCERT setting. That's why you never ran into the problem before > :/ Sigh... Apparently nobody reads the part of the doc that says "there is no good reason to change this from the libldap default." >> All versions that I have tested (certainly back to 2.3.32) incorrectly >> fail to connect when the URL is ldap://localhost:1389/ and a CA cert >> is provided. > Yes, AFAIK libldap's behavior of trying to figure out the machines real > hostname when connecting to localhost and using that hostname to verify > the server's certificate is there since quite some time already. It will > only verify against "localhost" when it completely fails to get the > machines' real name. I always considered that a feature more than a bug. Agreed. Server certs are supposed to carry the host's FQDN. "localhost" is just a magic alias; in a cert it shouldn't be anywhere other than a subjectAltName. >>> I'll note that I just tested some localhost certs a few days ago and > they were >>> fine, and the cert verification code hasn't changed in quite a long > time. >>> >>> (E.g., ITS#6711 the test setup there uses localhost with no problem.) > But if I see it correctly it sets "TLSVerifyClient allow" on the master > and "tls_reqcert=never" on the consumer. So it doesn't really verify the > certificates. (I might have overlooked something, took only a brief > glance at it). Ah, that sounds familiar. Closing this ITS. It's not a regression and not a bug, just a long established feature. -- -- 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#6838) TLS client will not accept certificate for 'localhost'
by rhafer＠suse.de 18 Feb '11

18 Feb '11

Am Freitag 18 Februar 2011, 13:17:17 schrieb andrew.findlay(a)skills-1st.co.uk: > On Fri, Feb 18, 2011 at 12:30:25AM +0000, hyc(a)symas.com wrote: > > Used to work - since when, what release, what else has changed since > > then? > > Unfortunately I cannot tell you exactly when this changed. In any > case, the change only affects a different bug which was masking the > problem that I now see. > > I do know that 2.3.32 as shipped with SLES 10.3 masks the problem by > not checking the server certificate properly. So does 2.4.12 as > shipped with OpenSuSE 11.1. Both will allow ldapsearch -ZZ to connect > to *any* TLS-capable server if they do *not* have access to the CA > certificate. > > 2.4.24 built on OpenSuSE 11.3 (i.e. using OpenSSL 1.0) correctly > refuses to connect if there is no CA cert. Yes, older openSUSE releases used a bad (i.e. less secure) default for the TLS_REQCERT setting. That's why you never ran into the problem before :/ > All versions that I have tested (certainly back to 2.3.32) incorrectly > fail to connect when the URL is ldap://localhost:1389/ and a CA cert > is provided. Yes, AFAIK libldap's behavior of trying to figure out the machines real hostname when connecting to localhost and using that hostname to verify the server's certificate is there since quite some time already. It will only verify against "localhost" when it completely fails to get the machines' real name. I always considered that a feature more than a bug. > > I'll note that I just tested some localhost certs a few days ago and they were > > fine, and the cert verification code hasn't changed in quite a long time. > > > > (E.g., ITS#6711 the test setup there uses localhost with no problem.) But if I see it correctly it sets "TLSVerifyClient allow" on the master and "tls_reqcert=never" on the consumer. So it doesn't really verify the certificates. (I might have overlooked something, took only a brief glance at it). Ralf

1 0

Re: (ITS#6838) TLS client will not accept certificate for 'localhost'
by andrew.findlay＠skills-1st.co.uk 18 Feb '11

18 Feb '11

On Fri, Feb 18, 2011 at 12:30:25AM +0000, hyc(a)symas.com wrote: > Used to work - since when, what release, what else has changed since then? Unfortunately I cannot tell you exactly when this changed. In any case, the change only affects a different bug which was masking the problem that I now see. I do know that 2.3.32 as shipped with SLES 10.3 masks the problem by not checking the server certificate properly. So does 2.4.12 as shipped with OpenSuSE 11.1. Both will allow ldapsearch -ZZ to connect to *any* TLS-capable server if they do *not* have access to the CA certificate. 2.4.24 built on OpenSuSE 11.3 (i.e. using OpenSSL 1.0) correctly refuses to connect if there is no CA cert. All versions that I have tested (certainly back to 2.3.32) incorrectly fail to connect when the URL is ldap://localhost:1389/ and a CA cert is provided. > I'll note that I just tested some localhost certs a few days ago and they were > fine, and the cert verification code hasn't changed in quite a long time. > > (E.g., ITS#6711 the test setup there uses localhost with no problem.) Hmm - that seems to be server-to-server. My problem is with the client tools, so maybe a different code-path is used. I have put a small test case here: ftp://ftp.openldap.org/incoming/afindlay-localhost-tls-test-20110218.tgz The server cert is valid for 'localhost' and also for '127.0.0.1' The tests are: sh 1-plain Plain LDAP connection - no problems Connects to ldap://localhost:1389/ sh 2-tls-no-ca With TLS but client has no access to the CA cert so this should fail with a complaint about 'self-signed certificate' sh 3-tls-with-ca With TLS and access to the CA cert. Connects to ldap://localhost:1389/ This should succeed but it does not. sh 4-tls-with-ca-numeric With TLS and access to the CA cert. This one uses ldap://127.0.0.1:1389/ and succeeds. Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#6839) Expanded documentation for ldapi: and SASL EXTERNAL
by andrew.findlay＠skills-1st.co.uk 18 Feb '11

18 Feb '11

On Thu, Feb 17, 2011 at 04:21:35PM -0800, Howard Chu wrote: > >URL: ftp://ftp.openldap.org/incoming/afindlay-slapi-doc-patch-20110217a > This patch fails to apply to HEAD. Please re-read the contributing > guidelines; all patches must be against HEAD. It applies perfectly to the copy of HEAD that I downloaded this morning: andrew@slab:~/src/openldap-head> cvs -z3 checkout -P -rHEAD openldap ... much logging deleted ... andrew@slab:~/src/openldap-head> cd openldap andrew@slab:~/src/openldap-head/openldap> patch -b -p0 < ../afindlay-slapi-doc-patch-20110217a patching file doc/man/man8/slapd.8 patching file doc/guide/admin/runningslapd.sdf patching file doc/guide/admin/sasl.sdf patching file doc/guide/preamble.sdf Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#6829) Auditlog Mod Patch
by masarati＠aero.polimi.it 18 Feb '11

18 Feb '11

> Full_Name: Kyle Smith > Version: 2.4.24 > OS: Ubuntu 10.04 > URL: > http://faculty.ycp.edu/~ksmith8/patches/servers-slapd-overlays-auditlog.c.p… > Submission from: (NULL) (192.245.87.12) > > > This is an enhancement of the auditlog overlay. By using a new directive, > auditlog_single_line, the auditlog is outputted on a single line, instead > of the > normal ldif style. I needed to make this change so that our log indexer > doesn't > have to parse lots of ldif data, instead it will just index the fields as > written. This will also give the benefit of reduced filesize of the audit > logs, > as it shortens the record by a fair number of characters. > > How To configure: > > Add "auditlog_single_line" to the "overlay auditlog" configuration in > slapd.conf. I think this contribution is not acceptable, since by violating the LDIF specs it makes the string unparsable. Remember that newline has a special meaning in LDIF, it separates tokens. If you need auditlogs to be single-line for some purpose, you should design a format that makes it parseable, to be generally useful. In any case, I believe OpenLDAP software's task is to make (useful) information available in a general format, and this is already accomplished by slapo-audotlog. If you need it in another format, you can easily post-process it later, without modifying the baseline code. p.

1 0

Re: (ITS#6838) TLS client will not accept certificate for 'localhost'
by hyc＠symas.com 17 Feb '11

17 Feb '11

andrew.findlay(a)skills-1st.co.uk wrote: > Full_Name: Andrew Findlay > Version: 2.4.24 > OS: OpenSuSE 11.3 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.97.25.132) > > > For various test and teaching purposes I have a set of OpenLDAP configs that run > small servers intended for local access only. As I run these on a wide variety > of machines and also give them to students to run on their own machines, all the > LDAP clients are set up to access the servers via the loopback interface: > typically ldap://localhost:1389/ > > Some of the configs use TLS. I have a local CA which issues simple server certs, > usually with 'CN=localhost' as part of the subject name. Since upgrading the OS > and OpenLDAP version of my main test environment I find that TLS connections are > failing: > My client scripts used to work: I think this was purely because earlier versions > of the TLS client code were less careful about checking certificates. > Specifically, the 'self signed certificate in certificate chain' error was not > even reported unless client-side debugging was turned on. Used to work - since when, what release, what else has changed since then? I'll note that I just tested some localhost certs a few days ago and they were fine, and the cert verification code hasn't changed in quite a long time. (E.g., ITS#6711 the test setup there uses localhost with no problem.) -- -- 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#6839) Expanded documentation for ldapi: and SASL EXTERNAL
by hyc＠symas.com 17 Feb '11

17 Feb '11

andrew.findlay(a)skills-1st.co.uk wrote: > Full_Name: Andrew Findlay > Version: 2.4.24 > OS: OpenSuSE 11.3 > URL: ftp://ftp.openldap.org/incoming/afindlay-slapi-doc-patch-20110217a > Submission from: (NULL) (88.97.25.132) > > > This documentation patch affects the Admin Guide and one manpage. > It gives information about the ldapi: transport and the use of SASL EXTERNAL > with it. > The SASL EXTERNAL section also contains a small expansion on the use of TLS. > This patch fails to apply to HEAD. Please re-read the contributing guidelines; all patches must be against 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs