topic Re: securetty/root login at console in Operating System - HP-UX

securetty/root login at console

Bryan_6 — Tue, 18 Feb 2003 16:51:44 GMT

All,

I realize there have been quite a few posts regarding this subject, but I seem to be having a problem for which I couldn't find any information.

I have set up my securetty file to restrict root login access exclusively to the console (the only line in the file is 'console' w/o quotes). However, when I try to login as root at the console, I get login incorrect. I've played with permissions on securetty which didn't help. I'm running a TCB environment and using HP's web console. It seems this is a trivial problem, but I can't see why it's failing. Does anyone have any ideas?

Re: securetty/root login at console

Sridhar Bhaskarla — Tue, 18 Feb 2003 17:04:23 GMT

Hi,

What is the syntax of /etc/securetty?. It should be just "console". I have seen people putting "/dev/console".

-Sri

Re: securetty/root login at console

Bryan_6 — Tue, 18 Feb 2003 17:09:03 GMT

All I have in there is console.

Re: securetty/root login at console

Sridhar Bhaskarla — Tue, 18 Feb 2003 17:11:28 GMT

Oops.. Lately I have been such a _

You did mention that console is only the line.

Do a "cat -v /etc/securetty" and see if there are any spaces before or after the word console.

-Sri

Re: securetty/root login at console

Darren Prior — Tue, 18 Feb 2003 17:15:28 GMT

Hi Bryan,

Could you login successfully as root before you put the securetty file into place?

regards,

Darren.

Re: securetty/root login at console

Bryan_6 — Tue, 18 Feb 2003 18:06:33 GMT

Alright, I just realized what I did wrong (talk about being a _!). I recently changed root password and, being the security-conscious kinda guy that I am, put in a bunch of 'special' characters, including the '@' symbol . Since I have no control over my terminal settings until after I login, and being that HPUX thinks the '@' symbol is something other than the '@' symbol (isn't it delete?), all my login attempts as root on the console failed. Once I changed this, it worked.

Thanks anyways for the different clues...