[PATCH] Add hostname to default env file

Jari Aalto jari.aalto at cante.net
Mon Sep 10 17:51:04 CEST 2007

* Mon 2007-09-10 Werner Koch <wk AT gnupg.org> INBOX
> On Sun,  9 Sep 2007 04:37, eric AT debian.org said:
>> And I've written this patch to appease him. Let me know what you
>> think. 
> This breaks existing installations.  What about using 

Not many; and certianly not seriously.

1) The change si limited. It affects only installation that use 
   --write-env-file with no options.
2) Restat takes care of this.

Announcing changes in release notes can be used to notify upgrading

>   gpg-agent --write-env-file ${HOME}/.gpg-agent-info-$(hostname) ...
> in the startup script?  

This was exactly the reason why bug was raised and Eric kindly submitted
a proposed. The current existing implementation was limited to a single
host only and the design did not foreseen other environments.

File with hostname (or FDQN) handles single host as well as NFS mounted

> Eventually we might want to store the socket files at a fixed location
> like /tmp/gnupg-$USER/foo-socket instead of having them at a variable
> place. What does the file system standard says about this?

No directoried outside of $HOME can't be used for interoperability. The
/tmp is machine specific directory and wonät work on network mounted

PLease take a look at the picture again.


Welcome to FOSS revolution: we fix and modify until it shines

More information about the Gnupg-devel mailing list