Package: gnome-keyring Version: 2.22.3-2 Severity: normal
Hello, gnome-keyring-daemon conflicts with libpam-ssh. libpam-ssh adds a DSA key to ssh-agent after authenticating with its password in GDM (a form of SSO). But once I'm up and running in KDE, gnome-keyring-daemon asks to unlock the DSA key when using ssh, ignoring the already unlocked key. I don't want gnome-keyring-daemon to interfere with already loaded keys, so that libpam-ssh's single-sign-on works. This whole mix-up with ssh-agent and gnome-keyring-daemon is rather messy. Where is this going? Is one of them deprecated? In short, I want libpam-ssh SSO to work. I don't want users to type their password once more into or store it with gnome-keyring-daemon. Thanks, Wouter PS: Where is gnome-keyring-daemon started from actually? I don't see it in Xsession, GDM session or startkde. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25 Locale: LANG=nl_BE.UTF-8, LC_CTYPE=en_GB.utf-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-keyring depends on: ii gconf2 2.24.0-7 GNOME configuration database syste ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit ii libc6 2.9-3 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-7 GNOME configuration database syste ii libgcrypt11 1.4.4-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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
