On further thought, it's possible that something closer to what
Bernhard wants (and incidentally more along the lines of what I was
thinking of in some of our discussions just after the initial port)
might be achievable with Cython.

FWIW, GPGME is basically C90 and we only recently started to use C99 variadic macros - they are a cpp feature, though.

CFFI has no real means of generating the needed bindings on the fly
like SWIG does, except via its ABI methods, but those are inferior to
what SWIG does. It also can't handle all the ifdefs (or really any of
the ifdefs) in gpgme.h.

The issue has been fixed in Kleopatra: https://commits.kde.org/kleopatra/15ce46717636cecd1c1b8949d12b0ab6c3fed69a

3.1.11

I am working on the Telesec Signature Card v2. I will add encryption support to gpgsm.

Please let us know which version of Gpg4win you are using.

Sorry, I don't know what kind of sample data that is. The reference keys have been provided by the RFC6637 author and are part of GnuPG's test suite; see (gnupg/tests/openpgp/samplekeys/ecc-sample-*).

We do this now always if --auto-issuer-key-retrieve is set. Also backported to 2.2

Generally nice looking patch and great improvement for performance.

I back ported @jukivili's changes back to 2.2 which gives a CFB decryption speedup of 25%. I also implemented AEAD _decryption_ in 2.2 to be prepared for mixed 2.2 and 2.3 version use. And AEAD is really fast compared to CFB. Willbe in 2.2.21.

Nope, I was wrong.

Thanks for the patch. However, this the getopt is unfortunately GNU specific which is the reason why the original code open coded the option parser.

Thanks for testing. It's actually an error of generating _unicode_mapping.c, which utf8.c includes.

Thanks for reporting; the code is really new and not yet fully tested.

Data (ie.e CMS) signatures do now also work.