After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 632813 - gnome-keyring-daemon sets SSH_AUTH_SOCK even when ssh support is disabled
gnome-keyring-daemon sets SSH_AUTH_SOCK even when ssh support is disabled
Status: RESOLVED NOTABUG
Product: gnome-keyring
Classification: Core
Component: general
2.31.x
Other Linux
: Normal major
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-10-21 18:00 UTC by Jeff Nathan
Modified: 2010-10-21 18:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeff Nathan 2010-10-21 18:00:18 UTC 
Platform: amd64
Release: Ubuntu 10.10

http://live.gnome.org/GnomeKeyring/Ssh says that gnome-keyring-daemon stealing the SSH_AUTH_SOCK from other programs can be disabled by setting the gconf key /apps/gnome-keyring/daemon-components/ssh to false. Unfortunately, this does not work, and while it may or may not prevent it from acting as an ssh agent, it still steals the SSH_AUTH_SOCK environment variable when it’s run.

Presumably, gnome-keyring-daemon should not be resetting the SSH_AUTH_SOCK environment variable when configured not to do so.  It especially should not do so upon the launch of every single login shell - this behavior is insidious.
Comment 1 Stef Walter 2010-10-21 18:34:03 UTC 
Fixed the wiki. Use gnome-session-properties to choose which components to enable.

Not sure what you mean by login shells and setting of environment variables...