lubuntu-desktop team mailing list archive

[urusha <664206@xxxxxxxxxxxxxxxxxx>]

Default lubuntu oneiric installation contains this package and there is
pam_gnome_keyring in /etc/pam.d/lxdm, so, that's not the case. But your
words remind me to look into /var/log/auth.log, and that's what I see
there:

gnome-keyring-daemon[1498]: couldn't set environment variable in
session: The name org.gnome.SessionManager was not provided by any
.service files

After quick googling I found theese bugs related to this issue: 
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/344014
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/344444
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/357346
https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/564831

They are mostly about xfce-session. So, it seems lxsession has exactly
the same problems.

Here is the patch to startlubuntu script that solves the problem. If it's considered that lubuntu contains gnome-keyring by default, this patch seems to be sufficient.
 

** Patch added: "export gk SSH_AUTH_SOCK via startlubuntu"
   https://bugs.launchpad.net/ubuntu/+source/lxde-common/+bug/664206/+attachment/2566783/+files/startlubuntu-gkssh.patch

-- 
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 myname@xxxxxxxxxxxx" 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 myname@xxxxxxxxxxxx" 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 myname@xxxxxxxxxxxx
  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