FWIW, the original idea with Pinentry was to have a stripped down Widget which allows to securely enter the password. For that we even replaced the Gtk text widget to have better control over the code path from keyboard to screen. After a few years more more more stuff was requested and meanwhile the QT version of the Pinentry is probably larger than the gpg-agent process.

VS-Desktop-3.2.94.481-Beta: We now bring up the German version for the SecOps, as we do not have an official translation yet. The document will be replaced when we have that

Works in VS-Desktop-3.2.94.481-Beta and you even see beforehand which algo will be used:

For command line, reported issues have been fixed; Confusions for wrong errors are gone, it correctly reports appropriate errors of:

• GPG_ERR_PIN_BLOCKED
• GPG_ERR_NO_RESET_CODE
• GPG_ERR_BAD_PIN

Do you think it's too difficult for a beginner to write a pinentry-gtk4?

VS-Desktop-3.2.94.481-Beta: same as for the Gpg4win version.
And there is a hint if you enter "hkps://something" that this is not the right format (that is included in Gpg4win 4.4.0, too)

VS-Desktop-3.2.94.481-Beta: the option is removed in the Kleopatra settings and the tags are shown in the main certificate list as well as in the tabs of the certificate details.

The Qt dialog on fullscreen is interesting and it gives me an idea. Maybe if we center its contents? (on GTK, of course)

The Signature Card V2.0 is automatically loaded in VS-Desktop-3.2.94.481-Beta.
Other Telesec Cards, too, though this might take quite a while (e.g. the NetKey 3.0 card) and often a new reload is required.

Still, it is possible to provide a simple password entry window with GTK4, and there could be a way to enable fullscreen mode for that.

VSD-Beta-481: Encrypting/signing with gpgtar on the cli and decrypting/verifying with Kleopatra works

I set this to resolved after a quick replay of the original report situation did not show any issue.
If it occurs again please reopen.

What is the status (or maybe better scope) of this ticket? Why was it set to the milestone 2.4.5?
I do not see any improvement in Kleopatra from Gpg4win 4.4 (with gpg 2.4.7) regarding the behavior when trying to unblock a card.

Reported gnupg channel on IRC.
An ascii armored file in question was: https://github.com/syncthing/syncthing/releases/download/v1.29.2/sha256sum.txt.asc

Fixed in: rGb1857a2836c9: gpg: Fix handling with no CRC armor.

When CHECKCRC == 0 (no CRC), ->any_data was not set, resulted

	no valid OpenPGP data found.

wrongly.

I think I can understand you, too much complexity.

In VSD Beta-481 the translation is missing

See this comment which is related to T4538:

Hm, "Names for the certificate" seems wrong to me. Shouldn't it better be "Names in the User IDs [of this certificate]"? I would leave of the part in [] as redundant. Likewise for the mail addresses.

Re-open, so that I can pursue constant-time modular exponentiation.

Thinking about this some more, i came up with some more ways of showing some nice-to-have information in the tooltips:

works in VS-Desktop-3.2.94.481-Beta

works for VS-Desktop-3.2.94.481-Beta, too

works with VS-Desktop-3.2.94.481-Beta

VS-Desktop-3.2.94.481-Beta: works, if no kleopatragroupsrc is found at the new location, the one at the old location is used.
This is only relevant in the case that after the update to this version GpgOL is used without starting Kleopatra in between.
Because when Kleopatra is started it will copy the kleopatragroupsrc from the old location to the new one. After that the config file in the old location is ignored.