Hi,
1. Any and all handshake messages may be broken up into several pieces
and sent in several records -> Is this system's work
(software/hardware) ?
It is the responsibility of the SSL software to create/handle this.
If I wish to simulate the behavior that each handshake message is in a record protocol, is it in reason ?
It is reasonable to generate SSL in that way. But if your software is going to handle SSL records and messages produced by other SSL implementations, your software cannot assume that other implementations will do that.
2. more than one message may be sent in a single record
I think some handshake message will be not sent in a single record
because of each message's order.
As you know, the full handshake has 3 parts, the client hello, then a sequence of messages from the server, and finally another sequence from the client. Those last two sequences each consist of a number of handshake messages, followed by a "change cipher spec" record and a finished message. It is typical that all the messages sent before the change cipher spec record are sent in one record.
BTW, hello messages for both client and server have SessionID (vary number from 0 to 32 bytes), how can I assume a number (or range) with reason for first transaction.
When a client first contacts a server, it has no session already established, so it sends zero bytes of session ID. The server sends a sesion ID to the client during that handshake. In subsequent handshakes, the client sends that same session ID to the server.
Thanks again,
-- Nelson B
_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
