Without really looking at your report: May it be that this is because Pinentry does not get the WAYLAND_DISPLAY variable as reported in T5016? This will be fixed in 2.2.22 which I hope to release this week.

The CRL states how long it is valid and we cache it for about that time.
OCSP responses are by definition not cachable but we allow for a clock skew of 10 minutes.

Was easier to fix than expected. Thanks for the report. Fix goes into 2.2.22.

[These damned typos in commit messages ;-)]

I implemented subkey collapsing in 2.3. It is enabled by default but you can disable it it with

The keyserver options control how gpg imports or exports keys to the keyservers. Thus they indeed belong into gpg.conf.

I guess you have a keyserver statement in your gpg.conf.
By using

Release done.

if a user decided to use the Web Key Directory, this should be used instead of falling back to whatever has been configured (nothing else by default)

What is the current encoding? OEMCP ?

Unicode file names will now also work - see T4083 and T5030

Unfortunately we can't help you here as this is not a GnuPG problem or one of software we maintain.

Done for master and 2.2.22 - libgpg-error 1.39 (not yet released) is required for the actual fix.

Good catch

The options now work as documented. More tests on Window are required and eventually we need to handle non-ascii characters in file names.

Fixed for 2.2.22

Thanks. Fixed for 2.2.22

Thanks for reporting. Fixed for 2.2.22. repeat==0 works like before and repeat>1 also (that is several passphrase pinentries will pop up).

I's say we should not do anything but solve that along with the move of all fd/fp/sock/HANDLE stuff to gpgrt to solve this at one place. We need that anyway to properly support Windows64. We won't be abale to do this for 2.3, though.

If you use

It is indeed a limitation. We added these options to support the Kleopatra GUI. To avoid problems with filenames with embedded newlines etc. Kleoptra uses a binary nuls to delimit filenames. And that is what we only support.

Thanks

No, c99 was never required. Meanwhile we use a few c99 features but those are supported without any compiler option.

Please try with out supplied CFLAGS or change them from

@JW: @gniibe explained you the problem and provided a fix (i.e. use correct specifiction of the directory names). Changes to Makefile.in are a no-go because that is a built file and a real fix would need to go into libtool. However, for a couple of reasons we do not want to update libtool (e.g. too many breakages in the past, we have out own fixes in for Windows). Thus we consider this bug closed.

We won't do such a interface now.

Mitigations are in place for quite some time now; see T4755.

Fix will be in 2.2.22. Thanks for the report.

It was actually moved to noninstall in 2006. The reason or this is a conflict between the version of gpgsplit in GnuPG 1.4 and 2.0. Back then it seemed easier to keep on using the gpgpslit from 1.4 because that version was installed anyway. At that time gpg was called gpg2 we changed this much later and probably forgot to switch also to the gpgsplit from GnuPG 2.