[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pam failure

On Mon, Feb 19, 2001 at 02:37:29PM -0700, David Bishop wrote:
> [from /var/log/messages]
> Feb 19 15:29:56 server1 login: FAILED LOGIN 1 FROM masquerade.micron.com FOR
> db, Authentication failure
> Feb 19 15:29:58 server1 login: FAILED LOGIN SESSION FROM
> masquerade.micron.com FOR (null), Conversation error
> This just started happening.  Any normal user will recieve a "login
> incorrect" message when putting in their username and password, and I had to
> edit the /etc/pam.d/login file to not check /etc/securetty in order to let
> root login at all (it was previously accepting logons but immediately dumping
> you back to getty without giving you a prompt).  Of course, this is a sudden
> problem, and all the other admins claim "we didn't do nuttin".	Any ideas?  I
> keep thinking it's a pam thing, cuz I hate pam ;-), but so far my
> troubleshooting has come up with naught.  

(Groan) You're *allowing* root to log in remotely? Root should 
never log in directly from anywhere but the console. Use ssh, with
properly propogated public keys if you have to log in as root, since it
will be encrypted. But only if you trust the remote host...


   >> Tim Sailer (at home)             ><  Coastal Internet, Inc.          <<
   >> Network and Systems Operations   ><  PO Box 671                      <<
   >> http://www.buoy.com              ><  Ridge, NY 11961                 <<
   >> tps@unslept.com/tps@buoy.com     ><  (631) 924-3728                  <<

Reply to: