gnome-keyring Using a predictable socket directory for
- From: Stef Walter <stefw gnome org>
- To: "gnome-keyring-list gnome org" <gnome-keyring-list gnome org>
- Subject: gnome-keyring Using a predictable socket directory for
- Date: Thu, 06 Mar 2014 18:54:04 +0100
gnome-keyring-daemon creates various sockets (such as a ssh-agent
socket, gpg-agent etc...).
Now that most systems have $XDG_RUNTIME_DIR [1] support, I'll be
updating gnome-keyring-daemon to use that directly, rather than create a
randomly named subdirectory.
This way we can get away from using setting a $GNOME_KEYRING_CONTROL
environment variable in the session. We'll also get predictable
$SSH_AUTH_SOCK and $GPG_AGENT_INFO variables, although for the time
being we'll still set them in the session environment.
This also means that by default only one gnome-keyring-daemon should be
running per-user. That's the case with lots of most other parts of
GNOME, and is really the only way to guarantee sane behavior.
The changes are here, and will be merged into git master shortly:
https://bugzilla.gnome.org/show_bug.cgi?id=725801
The $GNOME_KEYRING_PID will also be going away.
If you want the old behavior back, and want gnome-keyring-daemon to use
an alternate directory for sockets, start it with the
--control-directory=/my/favorite/directory option.
Cheers,
Stef
[1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
[Date Prev][
Date Next] [Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]