Sper sa te ajute asta:
http://www.unixuser.org/~haruyama/security/openssh/README.privsep_nihongo.txt


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.  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 -s /bin/false sshd

/var/empty should not contain any files.

apoi ./configure cu
  --with-privsep-path=xxx Path for privilege separation chroot
  --with-privsep-user=user Specify non-privileged user for privilege
separation

sau:
http://www.be.linux.org/pipermail/asbl-libre/2002-June/000316.html



















----- Original Message ----- 
From: "Liviu Petcu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 03, 2003 3:45 PM
Subject: [rlug] problema ssh dupa update


> Buna!
>
> Stie cineva de ce dupa update la mandrake 8.2 nu mai pot porni serviciul
> ssh si primesc explicatia: privilege separation user ssh does not
> exists...?
> Am verificat passwd, groups, shadow si gshadow si din toate lipsesc
> intrarile referitoare la sshd...
>
> Nu stiu ce se intampla. Rog cineva sa ma lumineze care ar fi
> rezolvarea.
>
> Multumesc!
> Liviu Petcu
>
>
>
>
>
> --- 
> Detalii despre listele noastre de mail: http://www.lug.ro/
>


_________________________________________________________
Acest mesaj a fost automat scanat de AntiVir Professional

--- 
Detalii despre listele noastre de mail: http://www.lug.ro/


Raspunde prin e-mail lui