Ruigu Electronic

TLS Handshake Process Explained

2025-12-04

Full Name: Transport Layer Security

Definition: TLS is a cryptographic protocol designed to provide secure communication over a computer network. It is the successor to the older SSL (Secure Sockets Layer) protocol, with TLS 1.0 being the first version released in 1999 to replace SSL 3.0. TLS encrypts data transmitted between clients and servers, ensuring confidentiality, integrity, and authentication of the communicating parties. It is widely used in applications like HTTPS (web browsing), email (SMTP/IMAP/POP3 over TLS), VPNs, and instant messaging.

Core Goals of TLS

ConfidentialityEncrypts data in transit using symmetric encryption algorithms (e.g., AES, ChaCha20), so even if intercepted, the data is unreadable to unauthorized parties. The symmetric key is securely exchanged between client and server using asymmetric encryption (e.g., RSA, ECDHE) during the handshake phase.
IntegrityUses hash functions with message authentication codes (HMAC, e.g., SHA-256) to verify that data has not been altered or tampered with during transmission. Any modification to the encrypted data will be detected immediately.
AuthenticationValidates the identity of the communicating entities via digital certificates. Servers typically present an X.509 certificate signed by a trusted Certificate Authority (CA) to prove their legitimacy. Mutual authentication (both client and server presenting certificates) is also supported for high-security scenarios.

TLS Handshake Process (Simplified)

The TLS handshake is a critical sequence of steps that establishes a secure connection before any application data is transmitted. For TLS 1.3 (the latest and most secure version), the process is optimized to reduce latency:

Client Hello: The client sends a message specifying supported TLS versions, cipher suites, a random value, and a list of extensions (e.g., ALPN for protocol negotiation).
Server Hello: The server responds with the selected TLS version, cipher suite, its own random value, and its digital certificate. For TLS 1.3, the server may also send a pre-shared key (PSK) if available, or initiate an ECDHE key exchange.
Key Exchange & Authentication: The client verifies the server’s certificate against a trusted CA. Both parties use the exchanged random values and key exchange parameters to generate a shared master secret, which is then used to derive the symmetric encryption and HMAC keys.
Finished: Client and server each send a “Finished” message encrypted with the derived keys, confirming that the handshake was successful and the secure session can begin.

Note: Older TLS versions (1.0/1.1/1.2) have a longer handshake with additional steps (e.g., server key exchange, client certificate request), which increases latency.

Key Components & Cipher Suites

Cipher Suite: A combination of algorithms used for key exchange, authentication, encryption, and integrity. For example, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 specifies:
- Key exchange: ECDHE (Ephemeral Elliptic Curve Diffie-Hellman, forward-secret)
- Authentication: RSA (server certificate)
- Encryption: AES-256-GCM (symmetric encryption with Galois/Counter Mode)
- Integrity: SHA-384 (hash function for HMAC)
Forward Secrecy (FS): A critical feature where each session uses a unique symmetric key. Even if the server’s private key is compromised, past sessions remain secure (supported by ECDHE and DHE key exchange algorithms).

TLS Versions & Security Status

Version	Release Year	Security Status	Key Improvements
SSL 3.0	1996	Deprecated (vulnerable to POODLE attack)	Original SSL final version
TLS 1.0	1999	Deprecated (weak cipher suites, vulnerable to BEAST attack)	Replaced SSL 3.0, standardized by IETF
TLS 1.1	2006	Deprecated	Fixed BEAST vulnerability, added AES-GCM support
TLS 1.2	2008	Recommended (widely supported)	Mandated SHA-2 hash functions, added ECDHE support
TLS 1.3	2018	Most Secure (optimal performance)	Simplified handshake (1-RTT), removed weak algorithms, mandatory forward secrecy