Around Mon, November 29, 2010 11:01:03 AM David Schwartz dav...@webmaster.com
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
On 11/29/2010 2:34 AM, A. N. Alias wrote:
I've been using IE, Chrome and Firefox as clients for a test SSL/TLS server.
This works fine with Firefox, which uses a single TCP connection for the TLS
handshake and subsequent communication. However, IE and Chrome seem often to
send different parts o
On Mon, Nov 29, 2010 at 02:34:29AM -0800, A. N. Alias 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.?
Thi
I've been using IE, Chrome and Firefox as clients for a test SSL/TLS server.
This works fine with Firefox, which uses a single TCP connection for the TLS
handshake and subsequent communication. However, IE and Chrome seem often to
send different parts of the handshake on different TCP connecti
