[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: TLS dumping core
On Sun, Oct 16, 2005 at 09:48:10AM -0700, Kurt D. Zeilenga wrote:
> This is likely related to the new lightweight dispatcher code.
> Please retry... I've committed some changes which might
> help here.
Unfortunately not. cvs update picked up a change in
servers/slapd/connection.c, but even after a full make distclean / configure
/ make depend / make / make install cycle, I still get this triggered by
ldapsearch -Z:
----------------------------------------------------------------------------
TLS trace: SSL_accept:before/accept initialization
tls_read: want=11, got=11
0000: 30 0c 02 01 02 60 07 02 01 03 04 0.........
TLS trace: SSL_accept:error in SSLv2/v3 read client hello A
TLS: can't accept.
TLS: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_srvr.c:585
connection_read(12): TLS accept error error=-1 id=0, closing
connection_closing: readying conn=0 sd=12 for close
connection_close: conn=0 sd=12
daemon: removing 12
Assertion failed: (SLAP_SOCK_IS_ACTIVE( s )), function slapd_set_read, file daemon.c, line 548.
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
----------------------------------------------------------------------------
And with ldaps:// I get:
----------------------------------------------------------------------------
connection_get(12)
connection_get(12): got connid=0
connection_read(12): checking for input on id=0
TLS trace: SSL_accept:before/accept initialization
tls_read: want=11, got=0
TLS: can't accept.
connection_read(12): TLS accept error error=-1 id=0, closing
connection_closing: readying conn=0 sd=12 for close
connection_close: conn=0 sd=12
daemon: removing 12
Assertion failed: (SLAP_SOCK_IS_ACTIVE( s )), function slapd_set_read, file daemon.c, line 548.
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
----------------------------------------------------------------------------
Are you able to reproduce the problem at your side, or is this something
FreeBSD-specific?
Regards,
Brian.