* Mon 2007-09-03 Eric Dorland <eric AT debian.org> INBOX > * Jari Aalto (jari.aalto AT cante.net) wrote: > >> Package: gnupg-agent >> Version: 2.0.0-5.2 >> Severity: minor >> >> Please enhance the --write-env-file to append current host to the filename: >> >> now : $HOME/.gpg-agent-info >> proposed: $HOME/.gpg-agent-info-<hostname> >> >> The motivation is that hosts usually use NFS mounted home directories and >> reading the current $HOME/.gpg-agent-info will not work in another host. >> >> >> Host X +----- host A >> | >> /home ---+----- Host B >> | >> +----- Host C >> >> If user log into all hosts: >> >> ssh [EMAIL PROTECTED] >> ssh [EMAIL PROTECTED] >> ssh [EMAIL PROTECTED] >> >> The initialization code in ~/.profile could work if --write-env-file wrote >> host specific files: >> >> $HOME/.gpg-agent-info-hostA >> $HOME/.gpg-agent-info-hostB >> $HOME/.gpg-agent-info-hostC >> >> It would be even better if the host portion used FDQN instead of the >> hostname(1). > > I'm not sure why you don't just use > --write-env-file=$HOME/.gpg-agent-info-$(hostname)? Why force the > filename? Or do you mean that the default file (ie when you don't > specify --write-env-file explicitly) should have the > hostname appended? Because that makes more sense to me.
The bug report concerned about the latter. That the hostname (or better FDQN), would be appended by default. When no --write-env-file is not specified. Jari -- Welcome to FOSS revolution: we fix and modify until it shines -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
