On Tue, 2005-11-08 at 23:58 -0600, Mike McCarty wrote:
Craig White wrote:
> On Tue, 2005-11-08 at 20:49 -0600, Mike McCarty wrote:
>
>>Craig White wrote:
>>
>>>On Tue, 2005-11-08 at 20:31 -0600, Mike McCarty wrote:
>>>
>>>
>>>>Craig White wrote:
>>>>
>>>>
>>>>>On Tue, 2005-11-08 at 20:18 -0600, Mike McCarty wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Craig White wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>----
>>>>>>>reassert the password...
>>>>>>>
>>>>>>>passwd freddy #assuming you change it back
>>>>>>> # re-enter password - watch out for caps lock
key
>>>>>>> # perhaps try a different password to make sure
>>>>>>> # the hash changes in /etc/shadow
>>>>>>>
>>>>>>>Craig
>>>>>>
>>>>>>Yep. Same symptoms. I cannot use login to log in as freddy, a
>>>>>>newly created user.
>>>>>
>>>>>----
>>>>>create another user...and try.
>>>>>
>>>>>did you ever manually edit /etc/passwd or /etc/shadow so perhaps
there's
>>>>>a mismatch between them?
>>>>
>>>>Nope. I only used useradd, userdel, passwd, usermod, and the Gnome
>>>>tools.
>>>>
>>>>I just tried with another user name, and it fails the same exact
>>>>way.
>>>
>>>---
>>>can you su ?
>>>
>>>su - freddy
>>>
>>>Craig
>>
>>Yep, no problem.
>>
>>In one window...
>>
>>
>>[root@Presario-1 root]# useradd freddy
>>[root@Presario-1 root]# passwd freddy
>>Changing password for user freddy.
>>New UNIX password:
>>Retype new UNIX password:
>>passwd: all authentication tokens updated successfully.
>>[root@Presario-1 root]#
>>
>>
>>In another window...
>>
>>[jmccarty@Presario-1 jmccarty]$ su - freddy
>>Password:
>>[freddy@Presario-1 freddy]$ pwd
>>/home/freddy
>>[freddy@Presario-1 freddy]$ whoami
>>freddy
>>[freddy@Presario-1 freddy]$
>>
>>The password I entered was, of course, freddy's.
>>
>>However, after exit back to myself,
>>
>>[jmccarty@Presario-1 jmccarty]$ login
>>login: freddy
>>Password:
>>Login incorrect
>>
>>
>>login:
>>
>>I used the same password that worked with su -
>
> ----
> then clearly your issue isn't with /etc/passwd or /etc/shadow but is
> with 'login' command itself which I have never used and a quick perusal
> of 'man login' tells me that there are circumstances which may affect
> login ability.
But man login also says that the special conditions are checked
before the prompt for password takes place.
$ ls /etc/usertty
ls: /etc/usertty: No such file or directory
How about this...
$ login jmccarty
Password:
Authentication service cannot retrieve authentication info.
$ whoami
jmccarty
$ finger jmccarty
Login: jmccarty Name: Mike McCarty
Directory: /home/jmccarty Shell: /bin/bash
On since Mon Nov 7 14:11 (CST) on :0 (messages off)
On since Mon Nov 7 16:53 (CST) on pts/2 from :0.0
1 day 6 hours idle
On since Mon Nov 7 15:20 (CST) on pts/3 from :0.0
23 hours 1 minute idle
On since Tue Nov 8 20:16 (CST) on pts/6 from :0.0
Mail forwarded to Mike.McCarty(a)sbcglobal.net
No mail.
No Plan.
What does "Authentication service cannot retrieve authentication info."
mean?
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
Just try and hit CTRL+ALT+F2 and at login prompt type freddy and his
password.
Worked just fine for me.
When you try to login from within bash, it somehow passes your uid for
user freddy, which is not true. As a consequence PAM will reject the
authentication.
Calin Cosma
=================================================
The man on tops walks a lonely street; the "chain" of command is often a
noose.