summaryrefslogtreecommitdiff
path: root/README.privsep
diff options
context:
space:
mode:
authorstevesk <stevesk>2002-06-26 00:43:57 +0000
committerstevesk <stevesk>2002-06-26 00:43:57 +0000
commit83dc5ddab318ba51232bc7afdd24ca440e857bf8 (patch)
tree0d89fc7bbf8806a5a65717e40456cc1dfe158ded /README.privsep
parenta192e61582e045c7f3f7bfcb58c24f51307d6d4a (diff)
downloadopenssh-83dc5ddab318ba51232bc7afdd24ca440e857bf8.tar.gz
- (stevesk) [README.privsep] more for sshd pseudo-account.
Diffstat (limited to 'README.privsep')
-rw-r--r--README.privsep12
1 files changed, 8 insertions, 4 deletions
diff --git a/README.privsep b/README.privsep
index dd8069a7..ced943f2 100644
--- a/README.privsep
+++ b/README.privsep
@@ -14,14 +14,18 @@ function.
When privsep is enabled, during the pre-authentication phase sshd will
chroot(2) to "/var/empty" and change its privileges to the "sshd" user
-and its primary group. You should do something like the following to
-prepare the privsep preauth environment:
+and its primary group. sshd is a pseudo-account that should not be
+used by other daemons, and must be locked and should contain a
+"nologin" or invalid shell.
+
+You should do something like the following to prepare the privsep
+preauth environment:
# mkdir /var/empty
# chown root:sys /var/empty
# chmod 755 /var/empty
# groupadd sshd
- # useradd -g sshd -c 'sshd privsep' -d /var/empty sshd
+ # useradd -g sshd -c 'sshd privsep' -d /var/empty -s /bin/false sshd
/var/empty should not contain any files.
@@ -54,4 +58,4 @@ process 1005 is the sshd process listening for new connections.
process 6917 is the privileged monitor process, 6919 is the user owned
sshd process and 6921 is the shell process.
-$Id: README.privsep,v 1.9 2002/06/26 00:25:48 tim Exp $
+$Id: README.privsep,v 1.10 2002/06/26 00:43:57 stevesk Exp $