[Lubuntu-desktop] [Bug 664206] Re: SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager
Installing libpam-gnome-keyring package solved the problem for me. ** Tags added: natty oneiric -- You received this bug notification because you are a member of Lubuntu, which is subscribed to a duplicate bug report (660003). https://bugs.launchpad.net/bugs/664206 Title: SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager Status in GNOME keyring services: Unknown Status in “gdm” package in Ubuntu: Invalid Status in “gnome-keyring” package in Ubuntu: Invalid Status in “lxde-common” package in Ubuntu: New Status in “lxdm” package in Ubuntu: Confirmed Bug description: Binary package hint: lxde-common SSH_AUTH_SOCK is not being properly set. (Or it is pointing to a sock that doesn't accomplish its job.) Expected behavior: You run "ssh myn...@mydomain.net" and the password manager opens a GUI to ask for the passphrase. Once unlocked, it remains unlocked until you log off. Moreover, at that moment of unlocking you can tell it to remember the passphrase forever so it gets automatically unlocked next time you login. Any other application that uses ssh-like connections will find this key unlocked as well. Observed behavior: You run "ssh myn...@mydomain.net" and it prompts you for the key passphrase in the terminal. You run it again, you are prompted again. Any other application that uses ssh-like connections will result in a passphrase prompt as well. How to reproduce: Enter Lubuntu session Open Passwords and Encryption Keys Create a Secure Shell key Configure this key to some domain you can ssh to Open a terminal and run ssh myn...@mydomain.net You are promted for a password in the terminal interface. Partial workaround: Here is a partial workaround for a terminal session: export SSH_AUTH_SOCK=`echo /tmp/keyring*/ssh` after the keyring-daemon has been loaded. But it only works within the same terminal session, not for other applications that launch ssh-like processes. Disclaim: it works for Lubuntu session inside a Ubuntu 10.04 install, with GDM as session manager. $ printenv SSH_AUTH_SOCK /tmp/ssh-PZgdl10603/agent.10603 $ ssh mydomain Enter passphrase for key '/home/leorolla/.ssh/id_rsa': [pressed ^C] $ export SSH_AUTH_SOCK=`echo /tmp/keyring*/ssh` $ printenv SSH_AUTH_SOCK /tmp/keyring-k3BQQd/ssh $ ssh mydomain Last login: Wed Oct 20 19:58:06 2010 from Your default printer is mydomain:leorolla> [blinking cursor!] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/664206/+subscriptions ___ Mailing list: https://launchpad.net/~lubuntu-desktop Post to : lubuntu-desktop@lists.launchpad.net Unsubscribe : https://launchpad.net/~lubuntu-desktop More help : https://help.launchpad.net/ListHelp
[Lubuntu-desktop] [Bug 664206] Re: SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager
I get the Gnome keyring prompt in Natty but it only happens with user accounts where Ubuntu One has been enabled. I didn't get the prompt in Ubuntu, it started after I switched to Lubuntu using Pure LXDE instructions [1]. Should I open a new bug or does it have the same root cause than this bug? [1] http://www.psychocats.net/ubuntu/purelxde -- You received this bug notification because you are a member of Lubuntu, which is subscribed to a duplicate bug report (660003). https://bugs.launchpad.net/bugs/664206 Title: SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager Status in GNOME keyring services: Unknown Status in “gdm” package in Ubuntu: Invalid Status in “gnome-keyring” package in Ubuntu: Invalid Status in “lxde-common” package in Ubuntu: New Status in “lxdm” package in Ubuntu: Confirmed Bug description: Binary package hint: lxde-common SSH_AUTH_SOCK is not being properly set. (Or it is pointing to a sock that doesn't accomplish its job.) Expected behavior: You run "ssh myn...@mydomain.net" and the password manager opens a GUI to ask for the passphrase. Once unlocked, it remains unlocked until you log off. Moreover, at that moment of unlocking you can tell it to remember the passphrase forever so it gets automatically unlocked next time you login. Any other application that uses ssh-like connections will find this key unlocked as well. Observed behavior: You run "ssh myn...@mydomain.net" and it prompts you for the key passphrase in the terminal. You run it again, you are prompted again. Any other application that uses ssh-like connections will result in a passphrase prompt as well. How to reproduce: Enter Lubuntu session Open Passwords and Encryption Keys Create a Secure Shell key Configure this key to some domain you can ssh to Open a terminal and run ssh myn...@mydomain.net You are promted for a password in the terminal interface. Partial workaround: Here is a partial workaround for a terminal session: export SSH_AUTH_SOCK=`echo /tmp/keyring*/ssh` after the keyring-daemon has been loaded. But it only works within the same terminal session, not for other applications that launch ssh-like processes. Disclaim: it works for Lubuntu session inside a Ubuntu 10.04 install, with GDM as session manager. $ printenv SSH_AUTH_SOCK /tmp/ssh-PZgdl10603/agent.10603 $ ssh mydomain Enter passphrase for key '/home/leorolla/.ssh/id_rsa': [pressed ^C] $ export SSH_AUTH_SOCK=`echo /tmp/keyring*/ssh` $ printenv SSH_AUTH_SOCK /tmp/keyring-k3BQQd/ssh $ ssh mydomain Last login: Wed Oct 20 19:58:06 2010 from Your default printer is mydomain:leorolla> [blinking cursor!] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/664206/+subscriptions ___ Mailing list: https://launchpad.net/~lubuntu-desktop Post to : lubuntu-desktop@lists.launchpad.net Unsubscribe : https://launchpad.net/~lubuntu-desktop More help : https://help.launchpad.net/ListHelp
[Lubuntu-desktop] [Bug 660003] Re: Did not proper start gnome keyring
*** This bug is a duplicate of bug 664206 *** https://bugs.launchpad.net/bugs/664206 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 664206, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 664206 SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager -- You received this bug notification because you are a member of Lubuntu, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/660003 Title: Did not proper start gnome keyring Status in “lxdm” package in Ubuntu: Incomplete Bug description: Binary package hint: lxdm eric@scylla:~$ lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 Could not use ubuntu-bug bout this package. Summary: Updated my eee from lubuntu 10.04 to 10.10. Now i have to reenter my umts pin every login, before the update this was done by gnome-keyring. The keyring works a bit, login to wifi works well with stored pass. --- Architecture: i386 DistroRelease: Ubuntu 10.10 EcryptfsInUse: Yes Package: lxdm 0.2.0-0ubuntu1-henry1 PackageArchitecture: i386 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.35-22.34-genusername 2.6.35.4 Tags: maverick Uname: Linux 2.6.35-22-generic i686 UnreportableReason: Dies ist kein echtes Ubuntu-Paket UserGroups: admin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/660003/+subscriptions ___ Mailing list: https://launchpad.net/~lubuntu-desktop Post to : lubuntu-desktop@lists.launchpad.net Unsubscribe : https://launchpad.net/~lubuntu-desktop More help : https://help.launchpad.net/ListHelp