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

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.

I merged Tobias's MR

We need to check what the current status here is. This has been in the 5.0 Betas for a while, so testing with 5.0-Beta369 will work

Fixed and backported for VSD 3.4

With a GNUPG-Home on another Partition (on the VMs shared folder with the host) the auto refresh after deletion additionally doesn't work for public keys or S/MIME certificates.

Lastly, pushed a change into gniibe/t7855 branch.
rGf861b2a33f96: gpg,gpgsm: Fix thinko for FP closing under no lock.

Fixed and backported for VSD 3.4

Backported for VSD 3.4

Backported for VSD 3.4

Backported for VSD 3.4

Fixed. When one of the lists/tables gets focus then NVDA should speak something like "<name of list> list" or "<name of table> tree view".

I pushed further changes into gniibe/t7855 branch.
rG2fe62809014e: gpg,gpgsm: Serialize write access to keybox/keyring to protect.

Note: QGpgMEWKDLookupJob uses an Assuan transaction with dirmngr.

We had considered and rejected adding below the above configuration a marked section (like e.g. with a frame) showing the options in the order they appear in the sign/encrypt window:

• Sign as
• Encrypt for me
• Encrypt for others
• Encrypt with password
• Encrypt / Sign each file separately