You're right...it did come off a little bit vague.
Either way, though, I'm not aware of any buffer overflows or exploits
that could cause the current version of OpenSSh to grant a rootshell,
so the individual SSH sessions being owned by root shouldn't be a
problem, at this point.
On Tue, 5 Dec 2
On Tue, 05 Dec 2000, Thornton Prime wrote:
> On Tue, 5 Dec 2000, K Old wrote:
>
> > Ok, I am in the same situation. I have installed the RPM for ssh 2.3 and
> > have started it. It is running under root right now, but I realize that
> > this might not be safe. How and is it necessary for me to
On Tue, 5 Dec 2000, K Old wrote:
> Ok, I am in the same situation. I have installed the RPM for ssh 2.3 and
> have started it. It is running under root right now, but I realize that
> this might not be safe. How and is it necessary for me to start it as
> nobody?
Any process that handles log
On Tue, 5 Dec 2000, Mike Burger wrote:
> The SSH daemon needs to run as root, in order to bind itself to the port
> (any port below 1000 needs to be accessed as root).
>
> The initial SSHD will spawn sshd sessions as needed...upon connection.
>
However, those other spawned processes are also o
The SSH daemon needs to run as root, in order to bind itself to the port
(any port below 1000 needs to be accessed as root).
The initial SSHD will spawn sshd sessions as needed...upon connection.
On Tue, 5 Dec 2000, K Old wrote:
> Ok, I am in the same situation. I have installed the RPM for ss
Ok, I am in the same situation. I have installed the RPM for ssh 2.3 and
have started it. It is running under root right now, but I realize that
this might not be safe. How and is it necessary for me to start it as
nobody?
Any help is appreciated.
Kevin
>From: "Cassell, Damon" <[EMAIL PR
