For such language tickets please give more information. What are your language settings? Not only in Kleo, the system language settings, too.

This works fine with my Yubikey. Maybe it's depends on the specific type of smartcard. What type of card are you using?

A side question: what are your language settings there?
Seems gpg gives it's error messages in German, Kleo in English

This can only be tested with the AppImage because on Windows we disable drag&drop of certificates.

• I might want to know the fingerprints of those unknown recipients to search for them (in the audit log I can't see, which of those fingerprints are unknown immediately)

Didn't happen on Linux (on my one and only attempt to reproduce). Will have to check on Windows.

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Not sure, if my test covers all cases (especially regarding cache): encrypted for alice with several ADSKs (local/card, v4/v5, several algos, 1 unknown = not in keyring).

• If the cert associated with the adsk is in keyring, the userid of this cert is shown.
• The number of unknown recipients (cert not in keyring) is shown at the end.

Makes sense to me. Possible optimizations:

• I might want to know the fingerprints of those unknown recipients to search for them (in the audit log I can't see, which of those fingerprints are unknown immediately)
• The cert used for decryption could be listed first

The option is still displayed on gpg4win-5.0.0-beta395 @ win11, probably the fix is not included yet.

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks mostly good to me on gpg4win-5.0.0-beta395 @ win11.

nvda speech viewer output:

Related Addresses  tab control
Related Addresses  tab  Alt+  R
Related addresses  list
edward.tester@demo.gnupg.com  not selected

speech viewer:

Search missing keys when verifying a signature  check box  not checked  Alt+  S
X.509 Directory Services  grouping
Directory services  list  This is a list of all directory services that are configured for use with X.509.

Right, it's the same with gpgol disabled. I set it to invalid.

But you are able to do this w/o gpgol being active?

Sounds good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

That's not surprising. The fix was made after GpgOL 2.6.7. And gpg4win-5.0.0-beta395 still seems to include GpgOL 2.6.6 only.

Tested on gpg4win-5.0.0-beta395 @ win10/win11

Mostly looks good to me on gpg4win-5.0.0-beta395 @ win11.

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Issue is still present in gpg4win-5.0.0-beta395 @ win11:

gpgol logs:

Maybe related to https://dev.gnupg.org/T7813

Looks good to me on gpg4win-5.0.0-beta395 @ win11

This was a regression introduced by my fix to make F5 work again and to ensure that it's displayed in the View menu (which itself was a regression of the menu changes made with T7579: Kleopatra: improve menu items).

Looks good to me on gpg4win-5.0.0-beta395 @ win11 (gpg 2.5.13).

The changes in libkleo and kleopatra are not included in gpg4win-5.0.0-beta395. Maybe the changes in gpg make the issue less likely. This should still be tested with the complete fix.

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11 (tested with/without keyboxd, 20 keygen rsa3072 each, with/without password)

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Looks good to me on gpg4win-5.0.0-beta395 @ win11

I'd sad we keep it as it is now (unless we see a regression). The real and only correct solution is the use of a daemon to serialize access.

Still, there is a fundamental problem with keydb locking.

• It only assures no-data-corruption.
• When a process doing write access, another process reading the resource may encounter a problem (inconsistent data read), since data could be changed while accessing.
  • Currently, write access may occur with keybox compress, this means that users are not safe to invoke multiple gpg/gpgsm simultaneously (to be sure).
    • It would be: only keybox compress when users explicitly ask.
  • We could introduce a lock to read access... BUT naively adding a lock (both for read and write or read-multiple-write-one) results possible deadlock in gpgsm
    • in gpgsm, gpgsm_walk_cert_chain and gpgsm_validate_chain access the resource of keydb in a way of:
      • While it has a handle kh, by find_up routine, it may call keydb_store_cert by callback routine; The callback does write access to the resource opening another handle.
      • Currently, it works because of no lock for read access and keydb_store_cert appends data at the end.

All changes in gniibe/t7855 are pushed into master.

Backported for VSD 3.4 since this is clearly a regression introduced with T7350 and the fix is zero risk.

Fixed. The check box has been removed from the "S/MIME Validation" tab.

Fixed and backported for VSD 3.4

Fixed in master: rGae431b04370f: w32:common: Take care of possible race on startup under Windows.