Around Mon, November 29, 2010 11:01:03 AM David Schwartz [email protected] wrote:
>> As an example, IE may connect and send a ClientHello. The server responds >with >> a ServerHello on the same socket. IE then replies with >> ClientExchange/ChangeCipherSpec/Finished, but not necessarily on the same >> socket. Instead, IE may establish a brand new TCP connection and send the >> messages over that -- all while the server is expecting the messages on the >> original socket. The server remains blocked on a recv() for that socket, >> waiting for data that will never come through it. > >If so, then the server is stupid. Why would a server that had two connections >ever remain >blocked in a 'recv' on one of them? Clients generally make no timeliness >guarantees, but >servers generally do. So it is almost never acceptable for a server to say "I >won't do job X >for client Y until I can do job Z for client T." Around Mon, November 29, 2010 9:25:13 AM Victor Duchovni [email protected] wrote: >This is not plausible. Yes, each connection's handshake messages were indeed coming in on one socket. However, I had a race condition that mixed up the sockets passed to the threads handling each connection. The debug spew had me convinced that pieces of the handshake were coming in over different sockets. Knowing that this is implausible certainly helped -- thanks. A. N. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
