FS#13986 - Gnome Keyring's SSH Agent doesn't work outside of GNOME desktop
Attached to Project:
Arch Linux
Opened by Smith Dhumbumroong (zodmaner) - Friday, 27 March 2009, 15:07 GMT
Last edited by Jan de Groot (JGC) - Sunday, 31 May 2009, 09:29 GMT
Opened by Smith Dhumbumroong (zodmaner) - Friday, 27 March 2009, 15:07 GMT
Last edited by Jan de Groot (JGC) - Sunday, 31 May 2009, 09:29 GMT
|
Details
Description:
After upgrade gnome-keyring package to version 2.26.0-1 from Testing repository, Gnome Keyring's SSH Agent stop working outside of GNOME desktop. In previous versions, the keyring's SSH Agent used to work on other DE/WM, such as Openbox. The keyring starts just fine on other DE/WM, but instead of creating both /tmp/keyring-<sth>/socket and /tmp/keyring-<sth>/ssh it only created the first one, thus no ssh support. Downgrade the package to version in extra repository (2.24.1-1) restored the functionality. Additional info: * package version(s) - gnome-keyring 2.26.0-1 * config and/or log files etc. - none Steps to reproduce: - Upgrade gnome-keyring to latest version from testing repository - Restart and try to use ssh to login to other machine, observed that the keyring isn't working |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 31 May 2009, 09:29 GMT
Reason for closing: Not a bug
Additional comments about closing: User needs to launch a dbus session bus. When not using gdm/kdm, user is responsible for it himself.
Sunday, 31 May 2009, 09:29 GMT
Reason for closing: Not a bug
Additional comments about closing: User needs to launch a dbus session bus. When not using gdm/kdm, user is responsible for it himself.
Edit:
I checked gnome-keyring sources, the ssh agent is a component plugin since 2.25.x. If nothing has been specified on the commandline using the -c option, gnome-keyring will read the enabled components from gconf in /apps/gnome-keyring/daemon-components/.
I checked gconf key /apps/gnome-keyring/daemon-components using gconf-editor and make sure that both ssh and pkcs11 key is enabled, but still the ssh agent won't work (still no /tmp/keyring-<sth>/ssh or /tmp/keyring-<sth>/pkcs11).
Using --daemonize --login --components=ssh,pkcs11 options, I try to start the daemon by put the line in .config/openbox/autostart.sh and start it manually from terminal. Both methods produce same result: Still no /tmp/keyring-<sth>/ssh (or pkcs11). Using --daemonize --login --components=ssh options also produces the same result.
I then tried to run gnome-keyring-daemon from terminal with out any arguments or options (just $ gnome-keyring-daemon). This time, the daemon success in creating both /tmp/keyring-<sth>/socket.ssh and /tmp/keyring-<sth>/socket.pkcs11, but still the ssh agent doesn't work.
The following is what was throw at me by gnome-keyring when I tried to run it from terminal without any options:
** Message: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
GNOME_KEYRING_SOCKET=/tmp/keyring-oL7nqt/socket
SSH_AUTH_SOCK=/tmp/keyring-oL7nqt/socket.ssh
GNOME_KEYRING_PID=5899
Maybe we need to have GNOME session manager running in order to use ssh agent?
Oh and bender02 have reported that with the rest of GNOME updated, now the keyring also didn't work in GNOME too (source: http://bbs.archlinux.org/viewtopic.php?pid=524063#p524063).
** Message: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
GNOME_KEYRING_SOCKET=/tmp/keyring-16xqN6/socket
SSH_AUTH_SOCK=/tmp/keyring-16xqN6/socket.ssh
GNOME_KEYRING_PID=6420
If I use GDM it works.
There's quite some important bugfixes included in 2.26.1, including a packaging bug on my side (the package contained two dbus service files for the same daemon). Please test this version, as it might solve your problems.
I tried to start gnome-keyring-daemon from ~/.xinitrc but it does not work. I need gnome-keyring for nm-applet and Zatto but both ask me for a password because gnome-keyring does not work.
# launches a session dbus instance
dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
after upgrade from 2.24 nm-applet [used in dwm] doesn't find stored wifi passwords.
adding this to .xinitrc:
source /etc/X11/xinit/xinirc.d/*
fixes it.
Status Unconfirmed -> Confirmed? Upstream bug?
-Seb