GET_HIDDEN deprecated in gpgv2
jaimefdez86 at gmail.com
Thu Mar 21 10:22:36 CET 2013
Thanks for the quick answer!
>In any case, the code you use is
>pretty fragile because it does not follow the rules for using
>--command-fd. See the GPA project on how to correctly use it.
I don't understand, I thought that GPA used GPGME not command line, so I
dont know how I should use command-fd. I want to avoid the use of pinentry
or any other external graphical tool.
2013/3/20 Werner Koch <wk at gnupg.org>
> On Wed, 20 Mar 2013 11:19, jaimefdez86 at gmail.com said:
> > But this doesn't work in gpgv2. Is there any reason? Thanks you in
> I assume you mean gpg version 2 and not the gpgv2 tool.
> GnuPG-2 (commonly installed as gpg2) uses the agent and its Pinentry to
> handle passphrases. Thus there is no direct way to change the
> passphrase in the way you did it. In any case, the code you use is
> pretty fragile because it does not follow the rules for using
> --command-fd. See the GPA project on how to correctly use it.
> BTW, for about 3 year gpg2 support the command --passwd which makes
> changing the passphrase much easier.
> If you really want to use --command-fd style interaction for any secret
> key stuff, you need to wait for the next beta of 2.1 which has a new
> feature to loopback the pinentry requests to gpg2 . See the git master
> for details.
> Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnupg-users