Lutz,
thanks for the input. I did exactly as you suggested made a simple
macro
to check s->s3 for the NULL condition and log the event, and try to recover the
session gracefully. It is possible that this is happening during a
renegotiation. I
also considered that *s could be getting s
On Mon, Apr 01, 2002 at 01:30:31PM -0500, Brad Barfield wrote:
> OpenSSL version: 0.9.6c
> OS: Linux 2.4.7-10
> EGCS-2.91.66
>
> I am seeing a crash in my SSL client application where the ssl->s3
> member is NULL. from my limited understanding of the code, this
> should never happen at the po
