Public bug reported: 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 [email protected]" 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 [email protected]" 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 [email protected] 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!] ** Affects: lxde-common (Ubuntu) Importance: Undecided Status: New -- SSH_AUTH_SOCK not being properly set: user has to type password even if saved in the password manager https://bugs.launchpad.net/bugs/664206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
