Moving the agent's socket to /var/run ?

Werner Koch wk at
Wed Feb 24 16:55:24 CET 2016

On Wed, 24 Feb 2016 03:13, dkg at said:

> Debian definitely has them.  they're a good idea, and i'd be happy to
> use them.

Great.  Do you expect a name conflict due to our socket names:


> The right place to try if XDG_RUNTIME_DIR is not available is
> /run/user/<uid>/

We would figure that out at runtime so that it will also work work if
/var/run is not a symlink to run.

> Is this going to be the new "standard socket" location?  If so, how

For Unix it should be the default for 2.1 unless a configure option is
used to revert to the old behaviour.  For Windows there is no need to
change it.

> should we help people transition who have already been running with the
> old "standard socket" location?

All proper applications should use gpgconf to find the agents sockets,
Except for redirect sockets the only problem I see is that an already
running agent would not be used by 2.1 and a running scdaemon might have
locked the smartcard.  However running an old agent with a newer gpg is
in any case not a good idea.

What to do with gnupg 2.0 ?  Backport the changes or keep using the old
system?  I'd say to keep the old system.

For 1.4, which uses gpg-agent mainly as a passphrase cache, I would
suggest to backport the change in a way that /var/run is tried before
~/.gnupg - it is only about the client code.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-devel mailing list