https://bugzilla.redhat.com/show_bug.cgi?id=1436961
David Gibson <dgibson(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(petersen(a)redhat.c |
|om) |
|needinfo?(dgibson(a)redhat.co |
|m) |
--- Comment #11 from David Gibson <dgibson(a)redhat.com> ---
Sorry I've taken so long to reply to this - I've been very busy at my day job
(and I have a limited workaround that makes the current situation almost
bearable).
So, in fact this *does* happen with an ordinary Mate session. And, to my
surprise, with a plain xmonad session. And with a GNOME3 session.
Everything now, appears to insist on using gnome-keyring as the ssh key agent,
despite the fact that it suffers a serious limitation (bug 1248916). It used
to be that if you disabled gnome-keyring's ssh agent component in the startup
programs you'd get the plain, working ssh-agent instead, but that's no longer
the case. The xsessions for MATE, xmonad, and xmonad-mate start gnome-keyring
with ssh agent enabled anyway.
At least xmonad-mate (forgot to check the others) does _start_ ssh-agent, but
SSH_AUTH_SOCK is pointing to gnome keyring instead, so it's not very useful (my
workaround is based on manually altering SSH_AUTH_SOCK in each shell I start).
GNOME3 seems to be even worse - when I disable gnome keyring from the startup
programs, I don't get any SSH_AUTH_SOCK at all.
--
You are receiving this mail because:
You are on the CC list for the bug.