The server sends its Certificate message (depending on the selected cipher suite, this may be omitted by the server).For example, if the client supports TLS version 1.1 and the server supports version 1.2, version 1.1 should be selected version 1.2 should not be selected. The chosen protocol version should be the highest that both the client and server support. To confirm or allow resumed handshakes the server may send a session ID. The server responds with a ServerHello message, containing the chosen protocol version, a random number, CipherSuite and compression method from the choices offered by the client.If the client can use Application-Layer Protocol Negotiation, it may include a list of supported application protocols, such as HTTP/2. If the client is attempting to perform a resumed handshake, it may send a session ID. A client sends a ClientHello message specifying the highest TLS protocol version it supports, a random number, a list of suggested cipher suites and suggested compression methods. Usually, after three steps' handshaking, a client will send a client hello to the server, like this: Luckily, after comparing the broken connection and correct ones, I found something quite strange. I used TCPDUMP to collection some information. In the end, I had to seek help from lower layer information. However, I don't think any of these cause my situation because all things seemed work OK.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |