| 1 |
On Thu, 19 Apr 2012 13:58:42 -0700, walt wrote: |
| 2 |
|
| 3 |
> > I upgraded to sys-auth/pambase-20120417 and sys-apps/shadow-4.1.5-r1 |
| 4 |
> > and found I couldn't login to a new session or use su. Rebooting only |
| 5 |
> > made the problem permanent, I had to SSH in to revert to |
| 6 |
> > sys-auth/pambase-20101024-r2 and sys-apps/shadow-4.1.5. |
| 7 |
> |
| 8 |
> I've never been clear on how ssh authenticates a new login. Why would |
| 9 |
> your ssh login be accepted? Did you ssh in as a user and su to root? |
| 10 |
|
| 11 |
That would have failed on su. It works because I have key authentication |
| 12 |
for SSH. Otherwise I'd have been screwed. |
| 13 |
|
| 14 |
> Anyway, just as another data point I did the same update today and have |
| 15 |
> no trouble logging in. Here are my useflags for comparison |
| 16 |
|
| 17 |
> Installed versions: 20120417!b(03:40:29 AM 04/19/2012)(consolekit |
| 18 |
> cracklib gnome-keyring pam_ssh sha512 -debug -minimal -mktemp -pam_krb5 |
| 19 |
> -passwdqc -selinux) |
| 20 |
> |
| 21 |
> Installed versions: 4.1.5-r1(03:41:02 AM 04/19/2012)(acl cracklib pam |
| 22 |
> -audit -nls -selinux -skey -tcb -xattr) |
| 23 |
|
| 24 |
Mine are the same except for gnome-keyring - I use KDE. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
The sergeant walked into the shower and caught me giving myself a |
| 31 |
dishonorable discharge. Without missing a beat, I said, "It's my dick |
| 32 |
and I can wash it as fast as I want!" |
Archives