gpg-agent (2.0.7) hardcodes usage of /tmp directory

[Diego 'Flameeyes' Pettenò]

Werner Koch <wk at gnupg.org> writes:

> On Sat,  8 Mar 2008 01:05, flameeyes at gmail.com said:
>
>> Unfortunately gpg-agent ignores the TMPDIR variable entirely and always
>> create its socket in /tmp.
>
> IMHO this is correct.  We are not using a temporary directory but a
> using /tmp as directory known to be local.  This is a requirement for
> creating a socket.  Consider the case the user would set TMPDIR to a
> remotely mounted file system on a very fast server; depending on the
> file system you would not be able to create a socket then.

Uhm, what does tell you that /tmp is certainly local? What about nfsroot
clients? /tmp might not be local either.

Otherwise, a solution would be to expect the setup to provide an
user-writable /var/run subdirectory and use that, which would be better
suited for sockets.

-- 
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: </pipermail/attachments/20080310/ddb26b11/attachment.pgp>