Tools and systems / historical milestone
OpenSSH enables privilege separation by default
Exact default-change release date; does not claim all prior or future privilege-escalation risks were eliminated.
OpenSSH 3.3 made privilege separation the default configuration.
Open this milestone in the interactive map ↗The release notes explicitly identify the default change and direct readers to the privilege-separation design. Separating work across privilege boundaries reduces how much code must execute with elevated authority.
This records a deployment-default milestone rather than the invention of privilege separation in general. Niels Provos’s later 2002 presentation explains the OpenSSH implementation as a concrete example.
Follow the connections
- OpenBSD announces OpenSSH — Later security architecture in the same implementation
- Niels Provos presents OpenSSH privilege separation — Research presentation explains the deployed privilege-separation design
Suggest a connection from this landmark ↗
Cite this entry
Cites this map entry. Original evidence is linked below.