From ce4b274aa1b0c584b0b863e888acb954d5040352 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lutz=20J=C3=A4nicke?= Date: Wed, 27 Feb 2002 08:08:57 +0000 Subject: SSL_clear != SSL_free/SSL_new --- doc/ssl/SSL_clear.pod | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'doc') diff --git a/doc/ssl/SSL_clear.pod b/doc/ssl/SSL_clear.pod index f0aa5e94eb..8e077e31c9 100644 --- a/doc/ssl/SSL_clear.pod +++ b/doc/ssl/SSL_clear.pod @@ -25,6 +25,25 @@ if L was not called for the connection or at least L was used to set the SSL_SENT_SHUTDOWN state. +If a session was closed cleanly, the session object will be kept and all +settings corresponding. This explicitly means, that e.g. the special method +used during the session will be kept for the next handshake. So if the +session was a TLSv1 session, a SSL client object will use a TLSv1 client +method for the next handshake and a SSL server object will use a TLSv1 +server method, even if SSLv23_*_methods were chosen on startup. This +will might lead to connection failures (see L) +for a description of the method's properties. + +=head1 WARNINGS + +SSL_clear() resets the SSL object to allow for another connection. The +reset operation however keeps several settings of the last sessions +(some of these settings were made automatically during the last +handshake). It only makes sense when opening a new session (or reusing +an old one) with the same peer that shares these settings. +SSL_clear() is not a short form for the sequence +L; L; . + =head1 RETURN VALUES The following return values can occur: -- cgit v1.2.3