Bug#790049: SSH_AUTH_SOCK no longer set in environment

2017-09-15 Thread Josh Triplett
Package: gnome-keyring
Version: 3.20.1-1
Followup-For: Bug #790049

This bug went away for a while, but seems to have recurred.
gnome-keyring is running, and /run/user/1000/keyring/ssh exists. If I
manually set SSH_AUTH_SOCK=/run/user/1000/keyring/ssh and then run ssh,
gnome-keyring pops up its key unlock dialog. But my session didn't have
this variable set by default.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-keyring depends on:
ii  dbus-x11 [dbus-session-bus]  1.11.16+really1.10.22-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gcr  3.20.0-5.1
ii  libc62.25-0experimental3
ii  libcap-ng0   0.7.7-3+b1
ii  libcap2-bin  1:2.25-1
ii  libgck-1-0   3.20.0-5.1
ii  libgcr-base-3-1  3.20.0-5.1
ii  libgcrypt20  1.7.9-1
ii  libglib2.0-0 2.54.0-1
ii  p11-kit  0.23.7-3
ii  pinentry-gnome3  1.0.0-2

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.20.1-1

gnome-keyring suggests no packages.

-- no debconf information



Bug#790049: SSH_AUTH_SOCK no longer set in environment

2015-06-26 Thread Josh Triplett
Package: gnome-keyring
Version: 3.16.0-2
Severity: normal
File: /usr/bin/gnome-keyring-daemon

Recently, I noticed that gnome-keyring's SSH agent no longer seems to
set SSH_AUTH_SOCK in the session environment.  I can see via ps that the
SSH component is running:

josh  2321  0.0  0.1 419788  8108 ?SLl  08:48   0:00 
/usr/bin/gnome-keyring-daemon --start --components=ssh

However, nothing sets SSH_AUTH_SOCK in the session environment anymore.
(I have no-use-ssh-agent in /etc/X11/Xsession.options temporarily, to
prevent ssh-agent from running, as I'd prefer to use the SSH agent in
gnome-keyring.)

I noticed this when automated invocations of SSH stopped working.  For
instance, I have mutt configured to use an SSH tunnel.  With
gnome-keyring's SSH agent configured, gnome-keyring prompts for the
passphrase when I run mutt.  With ssh-agent (without a manual ssh-add)
or no agent configured, mutt just says that the tunnel failed.  (One of
many reasons I prefer to use gnome-keyring: the automatic prompting and
adding.)

(As an aside, does gnome-keyring-daemon with --components contact a
running instance of itself and add that component, rather than running a
separate instance?  Because I only ever seem to have one
gnome-keyring-daemon running, and it seems non-deterministic whether
it's the one with --components=ssh or --components=gpg, yet all of the
sockets exist in /run/user/1000/keyring, and messages in the session log
seem to suggest that at least the SSH and GPG components are running.)



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.8.18-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-18
ii  libcap-ng0   0.7.6-1
ii  libcap2-bin  1:2.24-9
ii  libdbus-1-3  1.8.18-1
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.44.1-1.1
ii  p11-kit  0.23.1-2

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.16.0-2

gnome-keyring suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org