ubject: Re: Socket left in CLOSE_WAIT state...
-- Original Message --
To: (openssl-users@openssl.org)
From: Stuart Weatherby (stuart_weathe...@yahoo.ca)
Subject: Re: Socket left in CLOSE_WAIT state...
Date: 22/4/2010 5:18:48a
> Shutdown disables the ability to read, write (or
hew Allen
To: openssl-users@openssl.org
Sent: Wed, April 21, 2010 4:00:10 PM
Subject: Re: Socket left in CLOSE_WAIT state...
-- Original Message --
To: (openssl-users@openssl.org)
From: Stuart Weatherby (stuart_weathe...@yahoo.ca)
Subject: Re: Socket left in CLOSE_WAIT state...
Date: 2
-- Original Message --
To: (openssl-users@openssl.org)
From: Stuart Weatherby (stuart_weathe...@yahoo.ca)
Subject: Re: Socket left in CLOSE_WAIT state...
Date: 22/4/2010 5:18:48a
> Shutdown disables the ability to read, write (or both) on a
> socket. However, shutdown() do
, April 21, 2010 2:18:27 AM
Subject: Socket left in CLOSE_WAIT state...
Hi,
My code leaves sockets in the CLOSE_WAIT state after I free the SSL connection
(running on windows XP with OpenSSL 0.9.8e). After I'm done with the
connection I call SSL_shutdown and SSL_free, but that doesn't
Matthew Allen wrote:
if (Ssl)
{
SSL_shutdown(Ssl);
SSL_free(Ssl);
}
Yes as the other writer says, you may need to close out the BIO (which
is the thing holding the socket descriptor/handle). So the "Bio" object
you created you may need to clean
Looks like it needs a BIO_free_all(bio) or something similair.
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org]on Behalf Of Matthew Allen
Sent: Wednesday, April 21, 2010 5:18 AM
To: openssl-users@openssl.org
Subject: Socket left in
Hi,
My code leaves sockets in the CLOSE_WAIT state after I free the SSL connection
(running on windows XP with OpenSSL 0.9.8e). After I'm done with the
connection I call SSL_shutdown and SSL_free, but that doesn't close the socket
on the client side. My code's probably wrong, so tell me what I
