Re: PGG with multiple GnuPG keys

["Satyaki Das" <satyakid@stanford.edu>]

Simon Josefsson <jas@extundo.com> writes:

>         The problem is that pgg-gpg.el doesn't know, during
> decryption, that 7C06BDD9 is the same key as the key that eventually
> gets used by the OpenPGP implementation when you request the "satyaki"
> key when signing a message.  So it can't use the cached passphrase for
> "satyaki" that it knows for the 7C06BDD9 key.
> 
> I think the best solution would be to change `pgg-gpg-sign-region' to
> parse gpg's output (GOOD_PASSPHRASE) and find out what the key id was,
> and then cache your passphrase under that hex key id (and under the
> "satyaki" name).  Then the cache will work if you receive a message
> for the 7C06BDD9 key id.  I have installed the patch below.  Does it
> work?

Yes, it does. It caches both "satyaki" and "7C06BDD9" and that is
the right way.

> > So I have now customized pgg-default-user-id to 7C06BDD9 and that
> > avoids the repeated queries for my passphrase. Is this the right
> > solution?
> 
> It is "right" in the sense that it may work for you.  My goal is that
> only very few people will need to configure PGG; the default behaviour
> should be Right.

Yes, that is a worthy goal. I have removed the customization for
pgg-default-user-id now, thanks!

Satyaki