SSL/TLS handshake process in Cybersecurity - Full Explanation

Introduction

When you visit a website, your browser and the website need to agree on how to keep your information private and secure. This agreement happens through a series of steps called the SSL/TLS handshake, which sets up a safe connection before any data is shared.

Explanation

Client Hello

The browser (client) starts by sending a message to the website (server) saying it wants to connect securely. It shares the versions of SSL/TLS it supports, a list of encryption methods it can use, and a random number to help create secure keys.

The client initiates the secure connection by proposing security options and sharing a random number.

Server Hello

The website responds by choosing the SSL/TLS version and encryption method from the client's list. It also sends its own random number and provides its digital certificate, which proves its identity and contains its public key.

The server selects security settings and proves its identity with a certificate.

Certificate Verification

The client checks the server's certificate to make sure it is valid and issued by a trusted authority. This step ensures the client is talking to the real website and not an imposter.

The client verifies the server's identity by checking its certificate.

Key Exchange

Using the information exchanged, the client creates a secret key and encrypts it with the server's public key from the certificate. Only the server can decrypt this secret key with its private key. This key will be used to encrypt the data sent between them.

A shared secret key is securely created for encrypting the communication.

Finished Messages

Both client and server send messages encrypted with the new secret key to confirm that the handshake was successful. After this, the secure connection is established, and they can safely exchange data.

Both sides confirm the secure connection is ready to use.

Real World Analogy

Imagine two people meeting to share secret messages. First, one suggests ways to communicate secretly. The other picks the best way and shows an ID card to prove who they are. Then, they agree on a secret code only they know. Finally, they test the code to make sure it works before chatting.

Client Hello → Person A suggesting secret communication methods and sharing a random number

Server Hello → Person B choosing the method and showing an ID card

Certificate Verification → Person A checking the ID card to confirm Person B's identity

Key Exchange → Person A creating a secret code and locking it so only Person B can open it

Finished Messages → Both confirming the secret code works before starting to talk

Diagram

Diagram

┌─────────────┐           ┌─────────────┐
│   Client    │           │   Server    │
└──────┬──────┘           └──────┬──────┘
       │ Client Hello (versions, methods, random) │
       ├──────────────────────────────────────────▶
       │                                           │
       │          Server Hello (chosen method, random) │
       │          Certificate (public key)          │
       ◀──────────────────────────────────────────┤
       │                                           │
       │ Verify Certificate                        │
       │ Create secret key, encrypt with public key│
       ├──────────────────────────────────────────▶
       │                                           │
       │ Decrypt secret key                        │
       │                                           │
       │ Finished message encrypted with secret key│
       ◀──────────────────────────────────────────┤
       │ Finished message encrypted with secret key│
       ├──────────────────────────────────────────▶
       │                                           │
       │ Secure connection established              │

This diagram shows the step-by-step message exchange between client and server during the SSL/TLS handshake.

Key Facts

SSL/TLS Handshake → A process where client and server agree on security settings and create shared keys for encryption.

Digital Certificate → A file that proves a server's identity and contains its public key.

Public Key → A key shared openly to encrypt data that only the private key can decrypt.

Secret Key → A shared key used to encrypt and decrypt data during a secure session.

Certificate Authority → A trusted organization that issues digital certificates to verify identities.

Common Confusions

Believing the handshake itself encrypts all data.

Believing the handshake itself encrypts all data. The handshake only sets up the encryption keys; actual data encryption happens after the handshake completes.

Thinking the server's certificate contains the secret key.

Thinking the server's certificate contains the secret key. The certificate contains the public key, not the secret key, which is created during the handshake.

Summary

The SSL/TLS handshake is a step-by-step process that sets up a secure connection between a client and a server.

It involves exchanging messages to agree on encryption methods, verify identities, and create shared secret keys.

Once the handshake finishes, the client and server can safely exchange encrypted data.