Today, I tried to ssh somewhere, and got a graphical prompt for my SSH
key passphrase, which my ssh-agent already knows due to libpam-ssh. I
have gnome-keyring's ssh agent disabled:
$ gconftool-2 -g /apps/gnome-keyring/daemon-components/ssh
false
Yet gnome-keyring has set SSH_AUTH_SOCK to its own socket:
$ echo $SSH_AUTH_SOCK
/tmp/keyring-Fs202f/ssh
- Josh Triplett
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnome-keyring depends on:
ii gconf2 2.24.0-6 GNOME configuration database syste
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.9-1 GNU C Library: Shared libraries
ii libcairo2 1.8.6-2 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst
ii libgconf2-4 2.24.0-6 GNOME configuration database syste
ii libgcrypt11 1.4.1-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.18.4-2 The GLib library of C routines
ii libgtk2.0-0 2.12.12-1 The GTK+ graphical user interface
ii libhal-storage1 0.5.11-8 Hardware Abstraction Layer - share
ii libhal1 0.5.11-8 Hardware Abstraction Layer - share
ii libpango1.0-0 1.22.4-2 Layout and rendering of internatio
ii libtasn1-3 1.8-1 Manage ASN.1 structures (runtime)
Versions of packages gnome-keyring recommends:
ii libpam-gnome-keyring 2.22.3-2 PAM module to unlock the GNOME key
gnome-keyring suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Le jeudi 19 février 2009 à 14:49 -0800, Josh Triplett a écrit :
> Today, I tried to ssh somewhere, and got a graphical prompt for my SSH
> key passphrase, which my ssh-agent already knows due to libpam-ssh. I
> have gnome-keyring's ssh agent disabled:
>
> $ gconftool-2 -g /apps/gnome-keyring/daemon-components/ssh
> false
>
> Yet gnome-keyring has set SSH_AUTH_SOCK to its own socket:
This is a known issue, which is caused by the move of GConf to D-Bus.
With CORBA, it was possible to start the GConf daemon from the PAM
module, and it is not possible anymore.
The bug is already fixed for the upcoming GNOME 2.26. However the patch
is a bit too complex to be backported in a snap.
Cheers,
--
.''`. Debian 5.0 "Lenny" has been released!
: :' :
`. `' Last night, Darth Vader came down from planet Vulcan and told
`- me that if you don't install Lenny, he'd melt your brain.