On 2/15/2011 2:32 AM, Renato Botelho wrote:
On Mon, Feb 14, 2011 at 05:11:42PM -0800, Doug Barton wrote:
On 02/14/2011 06:24, Renato Botelho wrote:
Hi Doug,
After this update, i can't start gpg-agent with --daemon:
garga@botelhor:~> gpg-agent --daemon
gpg-agent[76223]: listening on socket `/tmp/gpg-9XORch/S.gpg-agent'
gpg-agent[76224]: gpg-agent (GnuPG) 2.0.17 started
setenv GPG_AGENT_INFO /tmp/gpg-9XORch/S.gpg-agent:76224:1
That isn't how gpg-agent is supposed to work. See
http://dougbarton.us/PGP/gpg-agent.html for more information. It's
certainly working for me, or I wouldn't have committed the update. :)
Actually i'm using keychain, and it starts gpg-agent. I tried to start
it manually with the same parameters of your script, daemon was started
but i got the same bus error and an error code was returned
garga@botelhor:~> gpg-agent --enable-ssh-support --daemon --write-env-file
gpg-agent[40337]: listening on socket `/home/garga/.gnupg/S.gpg-agent'
gpg-agent[40337]: listening on socket `/home/garga/.gnupg/S.gpg-agent.ssh'
gpg-agent[40338]: gpg-agent (GnuPG) 2.0.17 started
setenv GPG_AGENT_INFO /home/garga/.gnupg/S.gpg-agent:40338:1
setenv SSH_AUTH_SOCK /home/garga/.gnupg/S.gpg-agent.ssh
setenv SSH_AGENT_PID 40338
[1] 40337 bus error gpg-agent --enable-ssh-support --daemon --write-env-file
garga@botelhor:~> echo $?
138
Because of this error code, keychain assumes gpg-agent was not started
correctly. I'll try to dig into it and see if I figure out what's
happening.
The output above looks like you have the "use well-known socket" option
in gpg-agent.conf, or gpg.conf (or whatever it's called, not in front of
my FreeBSD system atm). Try toggling it and see what happens.
hth,
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[email protected]"
