Thanks. Applied to 2.2 and master.

I still don't think that it is correct. We would also need to turn fd from an int to a gnupg_fd_t (ie. a HANDLE under Windows) which requires other changes and should be done in the other parts of the code as well. assuan_sock_close also delegates to the system specific function and on Windows removes the fd also from the cygwin table. This may trigger other bugs so I'd like to keep it as it is to go with the code which has been in active use for a long time - at least for 2.2

0.2.0 was just released with support for GCM. Tested against openpgpkeys.pm.me

I am always glad to fix such bugs before a release (I am about to prepare 2.2.22).

rG4c8d5eb0bdd3: agent: Allow TERM="".

Mails crossed ;-)

Ah wait. This has been fixed in master a year ago but was not backported to 2.2; see T4137. I'll add it to the forthcoming 2.2.22. Thanks for the report.

The warning above is harmless. Both strings are actually the same but stem from different versions of the autotools helper scripts

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