Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt

[Ted Zlatanov]

On Fri, 04 Oct 2013 09:12:34 +0900 Daiki Ueno <address@hidden> wrote: 

>> OK, so there's no way to avoid the broken behavior in epg.el and any

DU> Well, though you say "broken behavior in epg.el", there's clearly a
DU> design change in GnuPG side if GnuPG 2.x behaves differently from GnuPG
DU> 1.x.

DU> You can search on the gpg lists with something like: "gpg agent all
DU> secret key", you will find that Werner wanted to move all the secret key
DU> operations from gpg to gpg-agent to provide more security.  That then
DU> ended up with that pinentry needs to be spawned by gpg-agent, not gpg.

DU> I think most of your complaint on epg.el are user error and
DU> misunderstanding of underlying technical concepts of GnuPG.

I see.  I'll find a solution that works for me without epg.el so that
there will be no errors and misunderstandings.

Thank you for your help.

Ted