On (25/06/02 18:59), Rick Moen didst pronounce:
>> I notice that, contrary to what the advisory says, installing the Debian
> Security Team's update package did _not_ create group sshd on my
> systems, so I did so myself. Priv sep does appear to work as described.
> (The advisory further confirms what you said about priv sep being the
> default even without the keyword.)
>It's actually _user_ sshd it tries to create. On the system here, it's
user sshd and group nogroup.
From the debian advisory:
<quote>
This package introduces a new account called `sshd' that is used in the
privilege separation code. If no sshd account exists the package will
try to create one. If the account already exists it will be re-used. If
you do not want this to happen you will have to fix this manually.
</quote>
--
Chat ya later,
John.
--
BOFH excuse #156: Zombie processes haunting the computer
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
