Obviously this is the updated to 2.2.49

ECC support for X.509 and in particular pkcs#12 format is limited. That is in general not a problem because such certificates are stored on a token and not on disk.

Also implemented for 2.2

Will be backported after 2.2.49

FWIW: The fix rO75f46829054e is part of GpgOL since 2.6.3

2.2 test can be done with GnuPG-VS-Desktop-3.3.90.12-Beta-Standard.msi from Sep 17

Interesting. That means to replace hundreds of scripts in an average organization :-(.

Backported to 2.2 but not yes tested with 2.2

Can you please repeat this with gpg4win-5-beta using the keyboxd and also using the pubring.kbx (i.e. w/o use-keyboxd in common.conf)?

Sorry, I don't know Fedora packaging details. Please ask on gnupg-users for help if you want to build gpa yourself on that platform. This bug report is only read by very few people but on gnupg-users you can get the attention of several thousand users and developers.

Your first two issues are no issues. This is just usual output from a configure run.

Uses gpgme-2.0.0 with the above mentioned patches. I have seen no problems in my quick tests.

For the full fledged Windows installer see https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta369/gpg4win-5.0.0-beta369.exe

Is that really the same bug? I would be interested in seeing a more detailed report. BTW, Windows or Linux? Used standard beta installer on Windows?

If this is indeed a bug it won't be fixed in gpg4win 4. Thus a test with gpg4win 5 beta is highly appreciated. It would also be interesting to see what what version of gpg comes with Git.

Note that disabling Auto-preview is not the default and has only been implemented to work around severe performance degradation with certain MalwareAnti-Virus software.

In contrast to gnupg22 master did not proper show OCB compliance - not everything has yet been forward ported. But we can do so now and test master by setting GNUPG_ASSUME_COMPLIANCE=de-vs