gpgme passphrase_cb (problem solved)
john at zultron.com
Fri Sep 14 20:20:57 CEST 2012
Hi Werner, glad to hear from you.
On 09/14/2012 10:46 AM, Werner Koch wrote:
> On Sat, 8 Sep 2012 19:09, john at zultron.com said:
>> I'm pretty sure now that this is correct: gpg2 password input cannot
>> be captured without the use of a gpg-agent.
> That is right. gpg2 conceptional does not know anything about the
> passphrase. This is all up to the gpg-agent. Version 2.1 even removed
> all passphrase support from gpg2.
By 'gpg2' I think you mean '/usr/bin/gpg2'. Thanks for clearing that up.
Is there anything different about '/usr/bin/gpg' distributed with gnupg
v2 that would allow gpgme's passphrase_cb mechanism to work? Or is
passphrase_cb something that only works with gnupg v1, and cannot be
made to work with gnupg v2?
At this point, that's the main unanswered question for me, and a
widely-known answer might help a number of pygpgme users.
More information about the Gnupg-users