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

Then I don't see how we can avoid this. It should be easy to reproduce this with gpgconf alone if you know how to use --change-options manually. Simply set the LDAP server that's already configured in the global config file.

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).

gpgconf does not know about the global config files. Nor does it known about things like gpg.conf-2 etc.

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

I guess this is easy to explain:

1. gpgconf/gpgme reads the LDAP server from the global config
2. You add a second LDAP server (I don't think it matters if it's the same as the one from the global config or different one)
3. When you save the LDAP server then gpgme/gpgconf writes both LDAP servers to the local config
4. When you now read the LDAP servers you get one from the global config and two from the local config

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.