210-250 · Question #197
To facilitate encrypted bulk data transfer using the TLS protocol, the shared secret key that is sent from the client to the server is encrypted with which key?
The correct answer is C. server's public key. In TLS RSA key exchange, the client encrypts the pre-master secret with the server's public key so only the server can decrypt it and derive the shared session key.
Question
To facilitate encrypted bulk data transfer using the TLS protocol, the shared secret key that is sent from the client to the server is encrypted with which key?
Options
- Aclient public key
- Bclient private key
- Cserver's public key
- Dserver's private key
How the community answered
(37 responses)- A3% (1)
- B3% (1)
- C86% (32)
- D8% (3)
Why each option
In TLS RSA key exchange, the client encrypts the pre-master secret with the server's public key so only the server can decrypt it and derive the shared session key.
The client public key cannot encrypt a secret intended for the server because the server does not hold the client's private key and therefore cannot decrypt it.
Using the client's private key would produce a digital signature readable by anyone with the client's public key, not a confidential message to the server.
The client encrypts the pre-master secret with the server's public key, ensuring only the server - possessing the corresponding private key - can decrypt it and complete the symmetric session key derivation, as specified in RFC 5246 for TLS handshake key exchange.
The server's private key is kept secret on the server and is used by the server for decryption, never by the client for encryption.
Concept tested: TLS RSA key exchange pre-master secret encryption
Source: https://www.rfc-editor.org/rfc/rfc5246
Topics
Community Discussion
No community discussion yet for this question.