| 1 |
On 04/19/2012 02:51 PM, Neil Bothwick wrote: |
| 2 |
> On Thu, 19 Apr 2012 13:58:42 -0700, walt wrote: |
| 3 |
> |
| 4 |
>>> I upgraded to sys-auth/pambase-20120417 and sys-apps/shadow-4.1.5-r1 |
| 5 |
>>> and found I couldn't login to a new session or use su. Rebooting only |
| 6 |
>>> made the problem permanent, I had to SSH in to revert to |
| 7 |
>>> sys-auth/pambase-20101024-r2 and sys-apps/shadow-4.1.5. |
| 8 |
>> |
| 9 |
>> I've never been clear on how ssh authenticates a new login. Why would |
| 10 |
>> your ssh login be accepted? Did you ssh in as a user and su to root? |
| 11 |
> |
| 12 |
> That would have failed on su. It works because I have key authentication |
| 13 |
> for SSH. Otherwise I'd have been screwed. |
| 14 |
|
| 15 |
That seems like a (possibly) helpful clue. When you downgraded, |
| 16 |
did you do etc-update again, or were you asked to? Did you run |
| 17 |
it after the original upgrade? |
| 18 |
|
| 19 |
I see that almost all of /etc/pam.d/* have today's date on them, |
| 20 |
the only exceptions being samba, sshd, imap, sudo, polkit-1, and |
| 21 |
start-stop-daemon. |
Archives