SSH_AUTH_SOCK is overwritten by gnome-keyring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-keyring (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello, I'm using ubuntu v14 with unity. The problem I'm having is with SSH_AUTH_SOCK. I want to create an X-session and have my unix socket set in SSH_AUTH_SOCK. The session is created successfully but if I open terminal into that session and see the content of SSH_AUTH_SOCK, its different from what I've set.
I investigated this issue and found that gnome-keyring checks if SSH_AUTH_SOCK is empty in /usr/share/
I deleted X-GNOME-
I downloaded the source code of gnome-keyring and found that it creates a SSH_AUTH_SOCK and sets it in it's environment(but for some reason when I check /proc/<
I've searched in internet and found that gnome-session might be involved in this. Downloaded the source code of gnome-sesison and it clearly parses X-GNOME-
capture output from gnome-keyring-
GNOME_KEYRING_PID env variables properly.
and as I understand(please correct me if I'm wrong) those two procceses (gnome-keyring and gnome-session) communicate with each other. gnome-session process checks if X-GNOME-
So it appears that gnome-keyring doesn't care what is in /usr/share/
What I basically want is to have my path set in SSH_AUTH_SOCK without setting X-GNOME-
P.S. On ubuntu v16 when I create session and open terminal in it, there is my path set in SSH_ATUH_SOCK.
My info -> https:/
description: | updated |
description: | updated |