gpg-agent shell variable output

Justus Winter justus at
Wed Oct 19 16:09:26 CEST 2016

Daniel Kahn Gillmor <dkg at> writes:
> On Wed 2016-10-19 07:36:50 -0400, Justus Winter wrote:
>> As I have demonstrated, the size of sun_path restricts the length of the
>> relative path to the socket.  It does *not* restrict the length of the
>> absolute path to the socket.
> I think you demonstrated that it's possible to create a socket with a
> longer name.  Do you have a technique for retrieving the filesystem
> location of a socket whose name is longer than sun_path?

No, and I don't see why that is necessary here.  getsockname is only
recently used by gpg-agent in case the sockets are given using
--supervised, and then we do not need to know their name to supervise
the sockets or to set some environment variable.

There are two more uses for the socket names, 1/ as a fallback file for
the pinentry to touch after messing with the tty (no idea what's going
on here, that's what the comment says), 2/ one can ask the gpg-agent for
the location of the agent's socket and the ssh socket using the
'getinfo' command, but I don't see any value in that because in order
to talk to the agent one needs to know the socket location, and the ssh
socket's name is easily derived from the socket name.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 454 bytes
Desc: not available
URL: </pipermail/attachments/20161019/19549f68/attachment.sig>

More information about the Gnupg-devel mailing list