Note: If you want to set this early in your program you need to make sure that there is only one thread running.

We have used this task for more than the usual release info, thus the new title. We will use
T5343 for the 2.3.0 release info.

and item 6. Now for more testing.

Except for T5341: gpgconf does not list default_pubkey_algo pseudo option anymore, this should be done.

Maybe have gpg-wks-client(or also --export-filter) print a warning if the filtered result has a key expiration different than the original key? That seems the simplest way tp approach the problem.

Following @turkja 's advice, here's a python script I wrote that does exactly that:

I posted patch-set to mailing-list. Please check if AUTHORS/LICENSES updates are ok.
https://lists.gnupg.org/pipermail/gcrypt-devel/2021-March/005120.html

Can you please also update AUTHORS and LICENSE files? I would also ask you to add

I've cleaned up the patch from D501 and tweaked the implementation a bit for performance. Here's patches attached:

Fixed typos and applied to master. Thanks.

That is a problem on the macOS side, for example with their PINentry tool. Sorry, we can't help you here.
In any case we won't support a gpg4win version released nearly 4 years ago.

See the release notes for GnuPG 2.2.17 (T4606 first item). You need to import your peer's signature from a different source; e.g. ask them to send you your signed key by mail.

Items 1 to 5 have now been resolved.

That it. Things works nicely for me. Won't be backported to 2.2 because this introduces minor changes in the behaviour.

So far -- unlike the previous patch -- this seem to help (but since the issues are infrequent I can't be entirely sure yet).

So we now get UTF-8 argv in all GnuPG modules. Globing has been enabled for gpg using our own globing code instead of the ASCII only "int _dowildcard = 1;" mingw way.

Ingo, as you are currently working on the config dialog, maybe you could also fix this issue on the way.

(For completeness, people don't know if there was no documentation change, so if anything strikes them as strange, they cannot say if this is because they don't have the right version of the documentation.)

Also:

org.kde.pim.kleopatra: "Backend error: gpgconf doesn't seem to know the entry for gpg-agent/Security/allow-mark-trusted"
org.kde.pim.kleopatra: "Backend error: gpgconf doesn't seem to know the entry for gpgsm/Security/auto-issuer-key-retrieve"

When opening the configuration dialog Kleopatra reports:

Backend error: gpgconf does not seem to know the entry for dirmngr/LDAP/LDAP Server
Backend error: gpgconf does not seem to know the entry for gpg/Keyserver/keyserver
Backend error: gpgconf has wrong type for dirmngr/LDAP/ldaptimeout: 2 0
Backend error: gpgconf does not seem to know the entry for dirmngr/LDAP/max-replies

The certificate selection dialog for file encryption certificates is now restricted to encryption keys of the selected key protocol. The "New..." button allows the creation of a key of the selected key protocol.