Thank you Michael, you are correct. Somehow I missed the 2.4.46 release.
This issue may be closed.
Norm Green
On 10/1/2018 2:38 AM, Michael Ströder wrote:
> On 10/1/18 6:18 AM, norm.green(a)gemtalksystems.com wrote:
>> Full_Name: Norman Green
>> Version: 2.4.45
>>
>> Unfortunately the layout of the BIO_METHOD struct changed in OpenSSL
>> 1.1.1 and the static initialization is now incorrect:
> CHANGES of release 2.4.46 contains this:
>
> -------------------------- snip --------------------------
> OpenLDAP 2.4.46 Release (2018/03/22)
> [..]
> Fixed libldap OpenSSL 1.1.1 compatibility with BIO_method (ITS#8791)
> -------------------------- snip --------------------------
>
> So your report might be a duplicate of this:
>
> https://www.openldap.org/its/index.cgi?findid=8791
>
> Ciao, Michael.
On 10/1/18 6:18 AM, norm.green(a)gemtalksystems.com wrote:
> Full_Name: Norman Green
> Version: 2.4.45
>
> Unfortunately the layout of the BIO_METHOD struct changed in OpenSSL
> 1.1.1 and the static initialization is now incorrect:
CHANGES of release 2.4.46 contains this:
-------------------------- snip --------------------------
OpenLDAP 2.4.46 Release (2018/03/22)
[..]
Fixed libldap OpenSSL 1.1.1 compatibility with BIO_method (ITS#8791)
-------------------------- snip --------------------------
So your report might be a duplicate of this:
https://www.openldap.org/its/index.cgi?findid=8791
Ciao, Michael.
Full_Name: Norman Green
Version: 2.4.45
OS: AIX
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (50.53.145.234)
in tls_o.c, the function tlso_sb_setup has this code on line 833:
bio = BIO_new( &tlso_bio_method );
which uses a statically allocated BIO_METHOD. Unfortunately the layout of the
BIO_METHOD struct changed in OpenSSL 1.1.1 and the static initialization is now
incorrect:
static BIO_METHOD tlso_bio_method =
{
( 100 | 0x400 ), /* it's a source/sink BIO */
"sockbuf glue",
tlso_bio_write,
tlso_bio_read,
tlso_bio_puts,
tlso_bio_gets,
tlso_bio_ctrl,
tlso_bio_create,
tlso_bio_destroy
};
In 1.1.1, this (internal) SSL struct looks like this:
struct bio_method_st {
int type;
char *name;
int (*bwrite) (BIO *, const char *, size_t, size_t *);
int (*bwrite_old) (BIO *, const char *, int);
int (*bread) (BIO *, char *, size_t, size_t *);
int (*bread_old) (BIO *, char *, int);
int (*bputs) (BIO *, const char *);
int (*bgets) (BIO *, char *, int);
long (*ctrl) (BIO *, int, long, void *);
int (*create) (BIO *);
int (*destroy) (BIO *);
long (*callback_ctrl) (BIO *, int, BIO_info_cb *);
};
--On Saturday, September 22, 2018 11:11 AM +0000 dcb314(a)hotmail.com wrote:
> Full_Name: David Binderman
> Version: 2.4.46
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (79.65.83.114)
Thanks for the report, this has been fixed.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Stephan Austerm.hle
Version: 2.4.46
OS: Linux (Debian unstable)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (77.20.232.53)
Consumer slapd emits endless
5babd9c4 do_syncrep2: rid=001 (4096) Content Sync Refresh Required
messages when the provider has an empty accesslog (because it was freshly setup
and nothing has been added/updated since then). This issue was mentioned back in
2013 (see http://www.openldap.org/lists/openldap-technical/201301/msg00229.html)
already but it looks like it was not reported.
The provider likewise logs
5babd9cf conn=1000 op=60677 SRCH base="dc=company,dc=com" scope=2 deref=0
filter="(objectClass=*)"
5babd9cf conn=1000 op=60677 SRCH attr=* +
5babd9cf conn=1000 op=60677 SEARCH RESULT tag=101 err=0 nentries=0 text=
for every attempt from the consumer to lookup records in the accesslog.
--On Tuesday, September 25, 2018 2:06 AM +0000 hyc(a)symas.com wrote:
>> Why the openldap client can not use TLS1.3?
>
> RedHat builds their OpenLDAP packages with MozillaNSS, not OpenSSL.
Incorrect. Their latest builds for RHEL7 use OpenSSL.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
nanmor(a)126.com wrote:
> Full_Name: Nancy Mo
> Version: openldap-clients-2.4.44-15.el7_5.x86_64
> OS: Redhat 7
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (106.38.0.87)
>
>
> Hi team,
>
> Linux server is redhat7, and installed Openssl-1.1.1 which is support for
> TLS1.3。
> I tried to connect a LDAP server which is used TLS1.3, the openldap client
> connection failed, if the server setting change to TLS 1.2, it can connected
> successfully。
> By the way, use the openssl s_client -connect HOSTNAME.com:636, it will use TLS
> 1.3, and connect successfully.
> In the ldap.conf, I have set two parameters:
>
> TLS_CACERTDIR /etc/openldap/certs
> TLS_REQCERT never
>
> Why the openldap client can not use TLS1.3?
RedHat builds their OpenLDAP packages with MozillaNSS, not OpenSSL.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--On Tuesday, September 25, 2018 1:46 AM +0000 nanmor(a)126.com wrote:
> Full_Name: Nancy Mo
> Version: openldap-clients-2.4.44-15.el7_5.x86_64
> OS: Redhat 7
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (106.38.0.87)
Hello,
The ITS system is for bug reports only. Please direct usage questions to
the openldap-technical list. I will note that I've tested OpenLDAP 2.4.46
with both startTLS and LDAPS using TLS 1.3 when compiled on both the server
and client side with OpenSSL 1.1.1 and it worked correctly. You will need
to provide significantly more information about your configuration/setup
when contacting the openldap-technical list for any further assistance.
I would also note that official support for OpenSSL 1.1.0 and later was not
added until the OpenLDAP 2.4.45 release, with further fixes in the OpenLDAP
2.4.46 release. Thus I would advise a first step of upgrading to OpenLDAP
2.4.46.
Warm regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Nancy Mo
Version: openldap-clients-2.4.44-15.el7_5.x86_64
OS: Redhat 7
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (106.38.0.87)
Hi team,
Linux server is redhat7, and installed Openssl-1.1.1 which is support for
TLS1.3。
I tried to connect a LDAP server which is used TLS1.3, the openldap client
connection failed, if the server setting change to TLS 1.2, it can connected
successfully。
By the way, use the openssl s_client -connect HOSTNAME.com:636, it will use TLS
1.3, and connect successfully.
In the ldap.conf, I have set two parameters:
TLS_CACERTDIR /etc/openldap/certs
TLS_REQCERT never
Why the openldap client can not use TLS1.3?
Thanks a lot.
beat regards
nancy