[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Parsing Debug Output

To: David Wheeler <david@kineticode.com>
Subject: Re: Parsing Debug Output
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Mon, 18 Oct 2004 15:46:30 -0700
Cc: Openldap list <OpenLDAP-software@OpenLDAP.org>
In-reply-to: <A22DEFD0-2154-11D9-BF1D-000A95B9602E@kineticode.com>
References: <497380E8-2144-11D9-BF1D-000A95B9602E@kineticode.com> <6.1.2.0.0.20041018151913.02f830c8@127.0.0.1> <A22DEFD0-2154-11D9-BF1D-000A95B9602E@kineticode.com>

At 03:25 PM 10/18/2004, David Wheeler wrote:
>On Oct 18, 2004, at 3:19 PM, Kurt D. Zeilenga wrote:
>>>TLS trace: SSL3 alert read:warning:close notify
>>Looks to me like TLS was closed for some reason.
>Hrm. Know of any reason why it would be closed?

Yes, many.  I suggest you enable some additional
logging to see what's going on.

Kurt

Follow-Ups:
- Re: Parsing Debug Output
  - From: David Wheeler <david@kineticode.com>

References:
- Parsing Debug Output
  - From: David Wheeler <david@kineticode.com>
- Re: Parsing Debug Output
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: Parsing Debug Output
  - From: David Wheeler <david@kineticode.com>

Prev by Date: Re: client writing, which to use: ldap_start_tls_s/ldap_set_option
Next by Date: Re: Parsing Debug Output
Index(es):
- Chronological
- Thread