[Bug 195550] Re: libpam-ssh doesn't unlock my key

2012-12-21 Thread Thomas Hotz
Confirming because it happens to several people. ** Changed in: libpam-ssh (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195550 Title: libpam-ssh doesn't

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-11-29 Thread Daniel T Chen
** Changed in: libpam-ssh (Ubuntu) Importance: Undecided = Low -- libpam-ssh doesn't unlock my key https://bugs.launchpad.net/bugs/195550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-11-16 Thread Fran Burstall
This issue only started to bite me after upgrading to intrepid. I note: 1. Turning off the ssh component of gnome-keyring under gconf (set /apps/gnome-keyring/daemon-components/ssh to false) no longer seems to work (I guess this is what has changed with intrepid). 2. Commenting out the line:

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-11-16 Thread Fran Burstall
More on this: I find that there is a known bug in intrepid's gnome- keyring that stops it from reading the gconf database. See https://bugs.launchpad.net/gnome-keyring/+bug/275010/comments/9 for a workaround that stops gnome-keyring from messing with ssh. ---Fran -- libpam-ssh doesn't unlock

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-10-22 Thread Harri
Seems that Valentijn's new config doesn't use libpam-ssh or pam-gnome- keyring at all. According to the README in libpam-ssh you should be able to login if your password unlocks the private key in your .ssh directory. So for testing I would recommend to set the passphrase on your ssh key to a

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-07-24 Thread Valentijn Sessink
OK, here's a fix that worked for my setup. Could you (other bug subscribers) check your /etc/pam.d/gdm and see what it says? My old config (NON working): #%PAM-1.0 authoptionalpam_group.so authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 auth

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-07-24 Thread Valentijn Sessink
I have the same problem. My pstree shows: ├─gdm───gdm─┬─Xorg With all Gnome-stuff hanging under gdm: Z gdm └─gnome-session─┬─bluetooth-apple ├─gnome-panel ├─gnome-settings-───{gnome-settings-}

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-07-24 Thread Simon Sprünker
Valentijn, I tried your new config. Unfortunately it does not work for me. Regarding you previous post: My gdm also starts an xsession. -- libpam-ssh doesn't unlock my key https://bugs.launchpad.net/bugs/195550 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-05-11 Thread Geert Altena
I'm seeing the same things as the two above posters. I have the same GDM pam.d conf. For me, this bug showed up yesterday after an upgrade from 7.10 to 8.04 using the regular 'upgrade' option of the upgrade manager. What is strange is that the pop-up window is not styled using my regular GTK-style

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-05-09 Thread Jeff
I believe I am seeing the same bug. Attempts to add my ssh key to the ssh-agent fail with Could not open a connection to your authentication agent. Here is my /etc/pam.d/gdm: #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequired

[Bug 195550] Re: libpam-ssh doesn't unlock my key

2008-04-07 Thread Robbert
This bug still exists... -- libpam-ssh doesn't unlock my key https://bugs.launchpad.net/bugs/195550 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com