On Fri, 24 Nov 2006, Werner Koch wrote:
That is how you use gpg-agent. Really, it is a plug-in replacement of
ssh-agent. It works different internally but at a user level it is
very simlar.
My talk about ssh-agent may have induced you in error. My fault.
I was not comparing ssh-agent with g
x27;s nothing to do. (I'm not a C programmer, and even if I could I
woudn't try to hack such an important package!)
Thanks everyone.
--
Jorge Almeida
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
ust that I'm using a package
not recent enough?
TIA,
Jorge Almeida
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
) and
then give the passphrase when asked for it. But the pinentry-program
entry in gpg-agent.conf decides whether I'm supposed to be in an X
session or not. (BTW, pinentry-curses didn't work for me. But that's not
the real issue.)
Is there an
:On Wed, 22 Nov 2006, Werner Koch wrote:
On Wed, 22 Nov 2006 10:05, [EMAIL PROTECTED] said:
I suppose Linux does the right thing wrt this issue. Correct?
Yes, unless there is a bug.
And the cache is also is secure memory, just like the passphrases.
Yes.
Thanks again.
--
Jorge
On Wed, 22 Nov 2006, Werner Koch wrote:
first question is whether the passphrase is kept in locked memory
(assuming the OS supports it), i.e, the passphrase is never send to disk
or swap. Is this correct?
Right. The passphrase (in all cases: when asking for the passphrase,
or when gpg-agent re
