Lutz Jaenicke wrote:
> On Sun, Feb 04, 2001 at 06:12:39PM +0100, Gil Peeters wrote:
> > After calling SSL_shutdown() is it still nesc to close the underlying
> > socket associated with the SSL Connection?
>
> SSL_shutdown() will only send the close-alert to the peer and switch the
> setting of the SSL to "shutdown mode".
> It does not touch the underlying connection, so: yes, you have to close the
> underlying socket connection yourself.
So closing the socket will not hurt. Will this be a problem if I want to re-use
the session??? i.e will closing the userlying socket cause problems when
re-using the session info.
>
>
> > Is it also nesc to free() the SSL stuct return from SSL_new() or is that
> > done somewher in the shutdown?
> Once you have called SSL_shutdown(), you can either free the SSL object
> via SSL_free() (call SSL_new() to obtain a new one later) or call
> SSL_clear() to reset the SSL object and make it ready for a new connection.
I notice in the code for SSL_free that the SSL_SESSION is also freed. (call to
SS_SESSIO_free). Will the SSL_SESSION still be 'cached' because I told the
SSL_CTX to cahce client sessions?
Thanks again.
--
-----------------------------------------
Gil Peeters
CANCAS I.T. (bvba)
Willemsstraat 2
3000 Leuven, Belgium
-----------------------------------------
JAVA and Distributed Object Specialists
-----------------------------------------
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
