The TLS handshake is the initial negotiation between a client (like a browser or tool) and a server to establish a secure connection over TLS (Transport Layer Security).

During the handshake, they agree on things like:

• the cryptographic algorithms (cipher suites),
• authenticate the server (and optionally the client),
• and derive shared secret keys so that subsequent communication is encrypted and secure.

Why It Matters (and What Can Go Wrong)

• The exact choices and order of cipher suites, extensions, TLS versions, etc., are like a fingerprint: anti-bot systems can analyze them and detect unusual or fake clients.
• If your client’s handshake looks strange (supports odd options, lacks common ones, or uses unusual ordering), you might be flagged or blocked.
• TLS 1.3 improves the process by combining or eliminating some steps, making the handshake faster and more secure.

Relevance to Kameleo

Kameleo must mimic the handshake behavior of real browsers (supporting expected versions, cipher suites, extensions, etc.) so that its virtual browsers don’t stand out.