On Friday 29 April 2005 21.17, Alan Hadsell wrote:
Rikard Johnels
writes: sparhawk:/home/rikjoh # gpg-agent -v --daemon gpg-agent[32048]: Secure memory is not locked into core gpg-agent[32048]: NOTE: this is a development version! gpg-agent[32048]: listening on socket `/tmp/gpg-8Wz2dm/S.gpg-agent' GPG_AGENT_INFO=/tmp/gpg-8Wz2dm/S.gpg-agent:32049:1; export GPG_AGENT_INFO; rikjoh@sparhawk:~> echo $GPG_AGENT_INFO
And as the $GPG_AGENT_INFO contains nil, programs that rely on it malfunctions.
Any clues?
When you invoke gpg-agent, it sends output to STDOUT, which needs to be interpreted by your shell to create the environment variable. See
that line:
GPG_AGENT_INFO=/tmp/gpg-8Wz2dm/S.gpg-agent:32049:1; export GPG_AGENT_INFO;
above? That was supposed to be input to your shell. You can make that happen by doing:
,----
| sparhawk:/home/rikjoh # eval `gpg-agent -v --daemon`
`----
The "eval `x`" means that the command x will produce some output, which I want to send to the shell as input.
Because gpg-agent is running in a separate process, this is the only way it can set an environment variable in your shell.
-- Alan Hadsell If brute force doesn't work, you aren't using enough. Does that mean that gpg-agent fails to export the $GPG_AGENT_INFO if it is started in the bootprocess?
I dont care how it exports its values as long as it works. And now it doesnt! -- /Rikard " Sharing knowledge is the most fundamental act of friendship. Because it is a way you can give something without loosing something." -R. Stallman --------------------------------------------------------------- Rikard Johnels email : rikjoh@norweb.se Web : http://www.rikjoh.com/users/rikjoh Mob : +46 735 05 51 01 PGP : 0x461CEE56 ---------------------------------------------------------------