On Thu, Aug 30, 2007 at 08:30:27AM -0700, Adam Richards wrote:
> > > If this works. the problem is due to gpg. To debug this, I
> > > suggest to use ktrace to tarce the system calls done by gpg.
> >
> > Alright, will do. I'll send relevant results of kdump of
> > If this works. the problem is due to gpg. To debug this, I
> > suggest to use ktrace to tarce the system calls done by gpg.
>
> Alright, will do. I'll send relevant results of kdump of
> ktrace.out soon.
Didn't get very exciting output of ktrace:
-
> > echo '...STARTING GPG-AGENT'
> > eval `/usr/local/bin/gpg-agent --daemon`
> > echo $GPG_AGENT_INFO >$HOME/.gpg-agent-info
>
> BTW, you can do this easier by using gpg-agent's --write-env-file option.
Nice tip! Thanks.
> 1. Run pinentry manually:
>
>$
~> env | grep GPG
GPG_AGENT_INFO=/tmp/gpg-GqplAN/S.gpg-agent:89498:1
GPG_TTY=/dev/ttypm
~> tty
/dev/ttypm
Any help would be greatly appreciated. :) I haven't had much
luck googling around. I do not
