The singular name Secure Socket Layer is a historical label for shielding one network socket, coined in the nineteen nineties.
This page is about how that name was used, while the protocol idea and its successor belong in a companion explanation.
How it works
Early writers used the singular word socket because the promise was to protect one connection between a client and a server.
Over time people also wrote a plural form of the same name, which can hide the fact that these labels point at one product history.
The old protocol line was retired, and Transport Layer Security became the successor that browsers actually speak today.
Remembering the singular name helps readers untangle old documentation without treating the retired design as current practice.
Concrete examples
- An old manual tells an administrator to enable the singular socket name on a web server from that decade.
- A certificate error text still mentions the old singular label even though the live handshake is newer.
- A glossary equates the singular label, the plural label, and the successor as if the names had never shifted.
Protective measures
- Read the singular name as history when you meet it in old manuals, and check what the system negotiates now.
- Retire configurations that still offer the obsolete protocol versions associated with that early name.
- Teach new staff that the successor name is the one current clients implement.
- Keep archived documents labeled as historical so nobody copies retired settings into a new deployment.