blob: 2120544c79730b1a58acb5a9089e48e0db0b7da4 [file] [log] [blame]
Damien Miller263d68f2002-06-22 00:45:50 +10001Privilege separation, or privsep, is method in OpenSSH by which
2operations that require root privilege are performed by a separate
3privileged monitor process. Its purpose is to prevent privilege
Damien Millera8e06ce2003-11-21 23:48:55 +11004escalation by containing corruption to an unprivileged process.
Damien Miller263d68f2002-06-22 00:45:50 +10005More information is available at:
Kevin Steves02281552002-05-13 03:57:04 +00006 http://www.citi.umich.edu/u/provos/ssh/privsep.html
7
Damien Miller263d68f2002-06-22 00:45:50 +10008Privilege separation is now enabled by default; see the
9UsePrivilegeSeparation option in sshd_config(5).
Kevin Steves02281552002-05-13 03:57:04 +000010
Kevin Stevesd4866362002-06-24 16:49:22 +000011When privsep is enabled, during the pre-authentication phase sshd will
Kevin Steves02281552002-05-13 03:57:04 +000012chroot(2) to "/var/empty" and change its privileges to the "sshd" user
Kevin Steves40b011c2002-06-26 00:43:57 +000013and its primary group. sshd is a pseudo-account that should not be
14used by other daemons, and must be locked and should contain a
15"nologin" or invalid shell.
16
17You should do something like the following to prepare the privsep
18preauth environment:
Kevin Steves02281552002-05-13 03:57:04 +000019
20 # mkdir /var/empty
21 # chown root:sys /var/empty
22 # chmod 755 /var/empty
23 # groupadd sshd
Kevin Steves40b011c2002-06-26 00:43:57 +000024 # useradd -g sshd -c 'sshd privsep' -d /var/empty -s /bin/false sshd
Kevin Steves02281552002-05-13 03:57:04 +000025
26/var/empty should not contain any files.
27
28configure supports the following options to change the default
29privsep user and chroot directory:
30
Damien Miller74cc5bb2002-05-22 11:02:15 +100031 --with-privsep-path=xxx Path for privilege separation chroot
Kevin Steves02281552002-05-13 03:57:04 +000032 --with-privsep-user=user Specify non-privileged user for privilege separation
33
Damien Millerc0e014d2005-06-05 09:21:41 +100034PAM-enabled OpenSSH is known to function with privsep on AIX, FreeBSD,
35HP-UX (including Trusted Mode), Linux, NetBSD and Solaris.
Kevin Steves02281552002-05-13 03:57:04 +000036
Tim Rice52879022004-06-27 20:50:35 -070037On Cygwin, Tru64 Unix, OpenServer, and Unicos only the pre-authentication
38part of privsep is supported. Post-authentication privsep is disabled
39automatically (so you won't see the additional process mentioned below).
Ben Lindstromc8c548d2003-03-21 01:18:09 +000040
Kevin Steves02281552002-05-13 03:57:04 +000041Note that for a normal interactive login with a shell, enabling privsep
42will require 1 additional process per login session.
43
44Given the following process listing (from HP-UX):
45
46 UID PID PPID C STIME TTY TIME COMMAND
47 root 1005 1 0 10:45:17 ? 0:08 /opt/openssh/sbin/sshd -u0
48 root 6917 1005 0 15:19:16 ? 0:00 sshd: stevesk [priv]
49 stevesk 6919 6917 0 15:19:17 ? 0:03 sshd: stevesk@2
50 stevesk 6921 6919 0 15:19:17 pts/2 0:00 -bash
51
52process 1005 is the sshd process listening for new connections.
53process 6917 is the privileged monitor process, 6919 is the user owned
54sshd process and 6921 is the shell process.