On 12/2/2010 2:36 AM, Aarno Syvänen wrote:
Hi List,
I have problem with SSL_shutdown. Advice seems to be to call it again, if the
return value is 0.
However, this means that shutdown can hang forever. Can I just call
SSL_shutdown and go on ?
You can go do other things and try to shut the con
Hi List,
I have problem with SSL_shutdown. Advice seems to be to call it again, if the
return value is 0.
However, this means that shutdown can hang forever. Can I just call
SSL_shutdown and go on ?
regards aarno
__
OpenSSL Pro
> Side track: Is it possible to make the window platform listen on > 31
> sockets at once per thread ? (or whatever is small limit was)
IOCP.
> Okay you closed your ears to the read event ? On Unix the select() has
> an exceptfds which can be used to pickup a socket error/close (but may
> not
the
client is doing.
4. The SSL client lose patience with a lack of response, and does an
SSL shutdown and socket close.
Okay you closed your ears to the read event ? On Unix the select() has
an exceptfds which can be used to pickup a socket error/close (but may
not be reliable if there
has an interest in, and
other events such as receiving data from other processes. At this time
it actually has no interest in any events at the socket, as it is
waiting for the processing to complete.
4. The SSL client lose patience with a lack of response, and does an
SSL shutdown and socket
Shaw Graham George wrote:
The problem is that, on Windows at least, my server doesn't appear to
get the "SSL shutdown notify" packet, for some reason. So, if that is
to be expected, I'm looking for an alternative way of detecting the
closure.
I've now tested it on Lin
Thanks for the response.
You'll have to bear with me, as I'm not really a low-level sockets
programmer. But maybe you misunderstood the nature of my problem.
The problem is that, on Windows at least, my server doesn't appear to
get the "SSL shutdown notify" packet,
Shaw Graham George wrote:
The sequence of events goes like this:
1. The SSL handshake proceeds as normal.
2. The client puts an HTTP request
3. The server gets the HTTP request
4. The client then executes an (unexpected) SSL shutdown
5. The server puts the HTTP response
Here I might
] On Behalf Of jimmy bahuleyan
Sent: 15 August 2007 14:01
To: openssl-users@openssl.org
Subject: Re: Problem handling unexpected SSL shutdown
jimmy bahuleyan wrote:
> Shaw Graham George wrote:
>> Hi,
>>
>> We have an application that provides HTTPS, either as client or
>> se
with one of our
>> customers, and there is a particular sequence of events, that involves
>> an unexpected SSL shutdown, that is giving an unexpected behaviour (at
>> least to me).
>>
>> The sequence of events goes like this:
>>
>> 1. The SSL handshake procee
icular sequence of events, that involves
> an unexpected SSL shutdown, that is giving an unexpected behaviour (at
> least to me).
>
> The sequence of events goes like this:
>
> 1. The SSL handshake proceeds as normal.
> 2. The client puts an HTTP request
> 3. The server g
George
Sent: 15 August 2007 11:38
To: openssl-users@openssl.org
Subject: Problem handling unexpected SSL shutdown
Hi,
We have an application that provides HTTPS, either as client or server,
for our customers. At the moment I am doing some testing between our
client and our server, as a result of a p
SSL shutdown, that is giving an unexpected behaviour (at
least to me).
The sequence of events goes like this:
1. The SSL handshake proceeds as normal.
2. The client puts an HTTP request
3. The server gets the HTTP request
4. The client then executes an (unexpected) SSL shutdown
5. The server
Message-
From: Matthew Shaylor
Sent: 07 November 2003 15:33
To: [EMAIL PROTECTED]
Subject: SSL Shutdown questions
Hi,
I'm trying to get to grips with the SSL protocol, in particular shutting down
conenctions gracefully. I've done some tests where I simply close down the socket.
If I
Hi,
I'm trying to get to grips with the SSL protocol, in particular shutting down
conenctions gracefully. I've done some tests where I simply close down the socket.
If I call SSL_shutdown after the socket has been closed then it allows the session to
be reused, otherwise it is marked as bad
15 matches
Mail list logo
