Eric Aksomitis wrote:
>
> Well, problem solved. For some reason by default the inet.d daemon
> wasn't running. I tacked him onto rc.local, and now it works.
>
> One question: How is it more secure to log in as a user and su to root,
> as opposed to allowing direct root access? The only thing I can see is
> that your root password will be buried in the middle of a bunch of
> packets, as opposed to being obviously spotted?
It's more secure because the hackers already know that there's a root
account; they just have to hack the password. But they don't know all
the other accounts. (Though by this logic, the "nobody" account surely
should be disabled as well--in fact all the "standard" accounts
should.) Does anybody know of another reason?
> My other question would be: why wasn't inet.d running by default?? It
> was totally installed and configured.
You didn't pick a server install?
Also, it would be more conventional to enabled it via linuxconf or your
favorite startup config, rather than adding it to local.
>
> Cheers
> Eric Aksomitis
>
> Charles Curley wrote:
> >
> > You should not be able to telent into the root account. It is considered
> > very insecure. You can telnet into a user account, then "su -" to run as
> > root. (Even more secure, use ssh instead, but that's another issue.)
> >
> > You didn't say whether you have tried to log in as a user; if not, try
> > that.
> >
> > What other functions are working or not working? Can you ping the beastie,
> > by host name or by IP address? Get the webpage?
> >
--
"Brian, the man from babble-on" [EMAIL PROTECTED]
Brian T. Schellenberger http://www.babbleon.org
Support http://www.eff.org. Support decss defendents.
Support http://www.programming-freedom.org. Boycott amazon.com.
