Bug 1401222 - SSH_AUTH_SOCK is set even when seahorse ssh agent is disabled
Summary: SSH_AUTH_SOCK is set even when seahorse ssh agent is disabled
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-03 16:39 UTC by Grégoire
Modified: 2017-12-12 10:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:56:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Grégoire 2016-12-03 16:39:19 UTC
Description of problem: Even when disabling gnome-keyring-ssh from starting with the session, the environment variable SSH_AUTH_SOCK is still set to /run/user/1000/keyring/ssh (which doesn't exist).

Version-Release number of selected component (if applicable): seahorse 3.20.0


How reproducible: every time


Steps to Reproduce:
1. Disable seahorse ssh agent by copying /etc/xdg/autostart/gnome-keyring-ssh.desktop to ~/.config/autostart/ and adding the line Hidden=true
2. restart
3. open a terminal
4. execute echo $SSH_AUTH_SOCK

Actual results: /run/user/1000/keyring/ssh


Expected results: It shouldn't print anything: the environment variable should be empty.


Additional info:
I reported this to the seahorse component as the gnome docs says "Gnome Keyring will set the SSH_AUTH_SOCK environment variable when it starts up." If it is an other component that actually sets the environment variable, tell me where to report.

Comment 1 David Gibson 2017-07-13 11:48:38 UTC
I suspect this has the same root cause as a problem I'm tracking in bug 1436961, where SSH_AUTH_SOCK is pointing gnome-keyring when it should be pointing at a standalone ssh-agent.

Comment 2 Fedora End Of Life 2017-11-16 18:55:49 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:56:29 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.