GPG homedir path length limit

Justus Winter justus at
Fri Feb 17 10:42:14 CET 2017

Daniel Kahn Gillmor <dkg at> writes:

> On Thu 2017-02-16 04:12:36 -0500, Justus Winter wrote:
>> That is still wrong.  The length of the path of the socket is not
>> limited in any way, the length of the path passed to connect is.
> this is a clever approach to *connect* to such a socket,


> on some systems.

Well, I tested it on all systems I had access to at that time.  I could
have written a small test program, and asked people to run it on systems
we don't have access to.  But we never got to that point :(

> But if you ever use getsockname (e.g. common/sysutils.c and
> dirmngr/dns.c), the long socket path names are bound to fail on *any*
> system, right?

Yes.  And iirc I went over why we use getsockname and figured that we
could do away with them.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: </pipermail/attachments/20170217/36fdea8e/attachment.sig>

More information about the Gnupg-users mailing list