# OpenSSH enables privilege separation by default

Tools and systems · 2002-06-21 · Security architecture enabled by default

OpenSSH 3.3 made privilege separation the default configuration.

Exact default-change release date; does not claim all prior or future privilege-escalation risks were eliminated.

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.

## Connections

- [OpenBSD announces OpenSSH](https://cyberhistorymap.com/records/openssh-public-announcement-1999/): Later security architecture in the same implementation
- [Niels Provos presents OpenSSH privilege separation](https://cyberhistorymap.com/records/niels-provos-privsep-wip-2002/): Research presentation explains the deployed privilege-separation design

## Sources

- [OpenSSH: original 3.3 release notes](https://www.openssh.org/txt/release-3.3)
- [USENIX: Provos privilege-separation presentation](https://www.usenix.org/conference/11th-usenix-security-symposium/preventing-privilege-escalation)

Stable entry ID: openssh-privsep-default-2002. Created by Cr8ivtek Inc.
