Am Mittwoch, 2. Januar 2008 schrieb Robin H. Johnson:
> On Tue, Jan 01, 2008 at 10:21:35PM +0100, Wolfgang Illmeyer wrote:
> To restate it more clearly from your paragraph above:
> kmail DEPENDS on gpgme built-with gnupg-2
> psi DEPENDS on gpgme built-with gnupg-1
> basket DEPENDS on gpgme built-with gnupg-1
Nope, psi does not depend on gpgme, it uses gpg directly - so it can use gpg1
while the gpgme stuff can use v2 at the same time.
> The best course of action here is fixing PSI and Basket to work properly
> with GnuPG2.
AFAIK they can't be, because they need to cache the passphrase, which is not
supported by gpg2. Does anybody know how passphrase caching works with gpg1?
Maybe it is possible to write some plugin/extension/patch to allow gpg2 to do
> The PSI issue was being tracked in bug 183075, but the users stopped
> providing information, and it worked from what alonbl could determine.
> I see it's open as bug 197588 again, hopefully we get enough user
> interaction to actually solve it now.
> I don't find any bug for Basket, could you please open one with your
> information about the problems you are having?
I'll have a look at the bugs today after work
> Also, could you confirm that you are indeed running the agent before any
> of the above stuff is started?
I'm confused - do you mean the password agent? Hasn't the password agent been
deprecated for a long time? I use pinentry for gpg2
What is the advantage
of running "the agent"?
email@example.com mailing list