The encyclopedia · Software & IT · Technical decision · 1994–2026
TLS wrapped security around TCP so every app got encryption unchanged
SSL/TLS sits between the transport and the application, so HTTP and other protocols gain privacy without changing a line of code.
Netscape · Internet Engineering Task Force
the move
Web shopping needed encryption and authentication, but retrofitting them into every application protocol would be slow and error-prone. The elegant move was to put a security layer just above TCP, where any higher protocol could use it.
Netscape invented SSL in the mid-1990s for this. A client and server negotiate a shared secret using certificates and public-key crypto, then encrypt everything in records, while the higher protocol keeps working unchanged.
The IETF standardized it as TLS, kept it application-protocol independent, and required only a reliable, in-order byte stream from the transport. That single property let the padlock spread to HTTP, SMTP, VoIP and far beyond.
why it works
- It requires only a reliable stream, so it runs on top of the transport everything already uses.
- It is application-protocol independent, so HTTP and others layer on it transparently.
- The handshake lets strangers agree on a secret without any prior shared knowledge.
what transfers
To make a hard capability universal, put it in the shared layer every protocol already sits on rather than in each protocol, and adoption follows for free.
what came after
TLS became the default security layer of the web, with the browser padlock and https making it consumer-facing. It has been steadily hardened, with TLS 1.2 in 2008 and TLS 1.3 in 2018, and browsers pushed HTTPS as a default, so ciphertext became the norm rather than the exception.
references
spotted an error? The archive wants to know.