Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was going to HTTPS communication over SSL. What I understood is both client and server do the handshake to obtain symmetric keys for application data encryption and decryption. My doubt is when a client sends a piece of encrypted data to server then how the server will identify the client and use the corresponding keys for decryption?

share|improve this question

As far as I know, it's the client's IP address and ephemeral port number that identify the connection to the application.

share|improve this answer

The SSL/TLS handhsake happens between the client and the server. At the end of the handshake, the client and the server will have established shared keys (and MAC secrets to ensure the integrity of the communication). In case of session resumption, a session identifier can be used to associate further connections with the same key.

The rest of the connection is identified using the normal TCP mechanism (assuming SSL/TLS over TCP).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.