-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2014 10:17 AM, lina wrote:
>
> surprised to see I have two processes.
>
> $ ps axjf | grep gpg
> 1 3980 3980 3980 ? -1 Ss1000 0:00
> /usr/bin/gpg-agent --sh --daemon --write-env-file
> /home/lina/.cache/gpg-agent-info
surprised to see I have two processes.
$ ps axjf | grep gpg
1 3980 3980 3980 ? -1 Ss1000 0:00 /usr/bin/gpg-agent
--sh --daemon --write-env-file /home/lina/.cache/gpg-agent-info
1 6109 6109 6109 ? -1 Ss1000 0:00 /usr/bin/gpg-agent
--sh --daemon --write-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2014 11:07 PM, lina wrote:
> Hi,
>
> I use icedove + enigmail for encryption with the pinentry-gtk2 as
> gpg-agent in the past.
>
> It worked well until yesterday I added a new email account with new gpg
> key for it.
>
> When the pop-up as
In addition, for the case I use pinentry-qt4,
$ ls -lrt /usr/bin/pin*
lrwxrwxrwx 1 root root 26 Jul 17 2013 /usr/bin/pinentry ->
/etc/alternatives/pinentry
-rwxr-xr-x 1 root root 152904 Jan 24 12:29 /usr/bin/pinentry-qt4
lrwxrwxrwx 1 root root 30 Jun 3 10:57 /usr/bin/pinentry-x11 ->
/etc
I also notice this
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=27;bug=401957
but not sure it is relevant. since it doesn't happen before.
and I am striving to find out where they save/cache the passphrase?
On Tue, Jun 3, 2014 at 11:07 AM, lina wrote:
> Hi,
>
> I use icedove + enigmail
Hi,
I use icedove + enigmail for encryption with the pinentry-gtk2 as gpg-agent
in the past.
It worked well until yesterday I added a new email account with new gpg key
for it.
When the pop-up asked for passphrase, I just can't input anything inside.
Later I tried the pinentry-qt4 and pinentry-
6 matches
Mail list logo
