Thanks Werner, I did that, saw the call to gpg2 (2.0.28, libcrypt 1.6.3), tried changing the engine to /usr/bin/gpg ( using gpgme_ctx_set_engine_info( ctx, GPGME_PROTOCOL_OpenPGP, "/usr/bin/gpg", NULL ) ) and that worked under Ubuntu.
Now, my target environment is CentOS 7, and they resolve /usr/bin/gpg with a link to /usr/bin/gpg2 - which does not play nice with set_passphrase_cb(). Any suggestions on the best way to untangle that knot? Mike On Thu, Mar 22, 2018 at 3:20 AM, Werner Koch <w...@gnupg.org> wrote: > On Wed, 21 Mar 2018 23:53, mangoc...@gmail.com said: > > > Which versions of gpg/gpgme support passphrase callback setting for > > symmetric encryption? My gpgme_check_version returns 1.5.5 and gpg > > --version returns 1.4.18 in Ubuntu 15.10 > > I doubt that it will work with 1.4. Note that gpgme prefers an > installed GnuPG 2 version and that may be an too old version or > combination of GnuPG 2 and gpgme. > > I would suggest that you run your application with > > GPGME_DEBUG=9:gpgme.log: ./your-application > > and check the created log file. It will have the used gpg version right > at the top and log the entire communication between gpgme and gpg. > > > Salam-Shalom, > > Werner > > > -- > # Please read: Daniel Ellsberg - The Doomsday Machine # > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
