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

[Neal H. Walfield]

On Fri, 26 Feb 2016 04:23:48 +0100,
Daniel Kahn Gillmor wrote:
> 
> On Wed 2016-02-24 16:55:24 +0100, Werner Koch <wk at gnupg.org> wrote:
> > On Wed, 24 Feb 2016 03:13, dkg at fifthhorseman.net 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:
> >
> >   S.gpg-agent
> >   S.gpg-agent.ssh
> >   S.scdaemon
> >   S.dirmngr
> >   S.uiserver
> 
> I don't forsee a name conflict with those names, but currently
> everything else on my own (admittedly non-standard system) uses a
> subdirectory (e.g. /run/user/$(id -u)/dconf/ and /run/user/$(id
> -u)/pulse/).

I think it would be a good idea to put the sockets in a gnupg
directory.NA

> What about for older-gpg and newer-agent combinations, though?  if an
> older gpg 2.1 tries to auto-launch a newer agent, and the agent listens
> on a different socket than gpg was expecting, they might never
> connect...

At least v2.0 and v2.1 are not supported together, so that scenario
shouldn't be a problem.  To support an old v1.4 with a new v2.1, we
could use assuan's socket redirection hack.

:) Neal