In my case (not Md Lazreg) I can control only client part of connection.
I use heavily patched OpenSSL 0.9.8d
The sever side use some version of MS WIndows. I believe it MS Server
2003 or newer.
I was hoping that the solution for Md Lazreg will help in my case.
Kyle Hamilton пишет:
I have solved my problem.
The problem in my case was a server one. I use a non-blocking socket for the
server to receive information from the clients, so the server performs a
select with a timeout of 1 second to read information. It turns out that
when they are network issues, 1 second is not
* Md Lazreg wrote on Thu, Jan 08, 2009 at 15:11 +0100:
The problem in my case was a server one. I use a non-blocking socket for the
server to receive information from the clients, so the server performs a
select with a timeout of 1 second to read information. It turns out that
when they are
I have the same problem with my client Openssl application. The server
side is MS IIS. And all other parties use Microsoft based clients and
have no such problems.
It seems that a client side is a source of trouble not a server side.
Suggestions from anyone are welcome.
Hi,
I have an SSL
Specifically, what versions of the MS operating system are you running
on the servers?
-Kyle H
On Wed, Jan 7, 2009 at 4:44 AM, Andrey Koltsov kolt...@cyberplat.com wrote:
I have the same problem with my client Openssl application. The server side
is MS IIS. And all other parties use Microsoft
Hi,
I have an SSL server handling many clients successfully using
openssl-0.9.8e. From time to time however, there are some clients that fail
to connect to it. Debugging shows that the problem happens when the client
attempts the first SSL_read, which unexpectedly returns 0.
Checking then for
