Point 1 from the list in the descryption seems to be covered.
Regarding point 2: Is there some visual feedback possible like in web forms when you type a not valid value?
And point 3 from the list: Ingo suggested to do the same as we do for the mail field when adding a UID or creating a key.

It is KF6.9.0 in Gpg4win-5.0.0-beta125

The formatted display of the symmetric passphrase is configurable: gpg-agent.conf option pinentry-formatted-passphrase

Ok, the behavior is different depending on if

Oh, then I mistakenly assumed that this behavior is the same in Gpg4win and GnuPG-VSD…
Then this seems to be by design although it does not make sense IMHO to handle this aspect differently between 4win und VSD.

I can find no difference between e.g. gpg4win-4.3.0 and 5.0-beta here:

• The window gets smaller when entering a password in both versions
• there is no whitespace between characters in the old version either

master is development and you can't expect that it always build on all platforms.

Here is a patch against master which normalizes line-endings when verifying text signatures over binary literal data packets

Not reproducible on Linux (with KF 6.11): When clicking the drop down triangle the popup briefly flashes (opens and immediately closes) before the error window is shown. Maybe the bug was fixed in the meantime. Needs to be checked.

In the spirit of making the UI less cluttered, I'd be in favor of removing this line entirely.

a) and b) are both entirely gpg's responsibility. I'm using --status-fd 2 --command-fd 2 to see which messages would be passed to/parsed by gpgme.

$ gpg --version
gpg (GnuPG) 2.4.8-beta10

Tobias: Maybe add the patch versioned for kwidgetsaddons-6.9.0 for now so that it can be evaluated early.

As of KF6.112, the datepicker will indicate invalid dates and not allow selecting them. We should update to that version, once it's out, or patch in c3f643639164914238dd8f19f03ea49298408293 of kwidgetsaddons

The point here is that I tried to reset with the resetting code, not with the Admin PIN.
As you said we do have an error code for the wrong reset code. Which does not come up.

We do not have an error code for Admin PINs. The Admin PIN is also an OpenPGP card specific termm and other cards use different terms. For example a NKS has no Admin PIN at all but an alternative PIN.

Ok, with VSD 3.3.0 and 4win 4.4.0 both I see

--import-options only-pubkeys

in a gpgme log when importing a key from WKD.

This is also causing problems with ostree, see https://bugs.debian.org/1098951 and https://github.com/ostreedev/ostree/issues/3386

I remove the milestone tag, as that one means "fixed in version 2.2.46" and added the general gnupg tag

With Gpg4win-Beta60 before the Gpg4win 4.4. release it was "reset code", see https://dev.gnupg.org/T5960#191665, seems there was a change after that

You could probably check that Kleopatra/gpgme calls gpg with the import option "only-pubkeys". For a real world test you'd have to upload a secret key to WKD.