According to Chris Rae: While burning my CPU.
>
> Hi - I'm new to this list so my apologies if this has been covered
> recently. I'm a computer-type but a Linux newbie so please bear with me!
> :-)
You have had many suggestions, most said use 'su' none said use 'su - root'
to include a PATH, anyway the point is only one person said, "Its still evil
to use 'su'," as "anyone" spying see's your passwd for "root", i found the
comment, "practice safe networking" ammusing and well spoken.
The file which stops root from logging in is "normaly" /etc/securetty.
/etc/login.* files could be tweeked to do it also.
I like the rest say DONT allow root in via a remote session, disaster
lurks, be warned.
>
> I have a Linux machine set up using RedHat which works very well. I have
> it networked with two PCs running Windows 95 and what I want to do is get
> a telnet session to my Linux box from one of my Windows 95 machines. I can
> telnet to it and log in as a user but I can't log in as root. I'm as sure
> as I can be that this is due to some sort of configuration thing in
> /etc/securettys or /etc/hosts.deny and /etc/hosts.allow - am I right? And,
> if so, what do I do to them?
>
> Sorry again for the question - it may seem trivial but my Linux machine is
> percherd on top of my wardrobe and I really need to log in remotely if I
> want to use it at all. :-)
>
> Chris
>
> +--------------------------------------+-----------------------------+
> | WWW: http://www.tardis.ed.ac.uk/~clr | "Five in every four just
> +--------------------------------------+ won't amount to nothing
> more" - Frank Zappa
>
--
Regards Richard.
[EMAIL PROTECTED]
