Often it is not desirable to use a keyserver,. However, not configuring one will fallback to a hardwired default OpenPGP keyserver. A new value "none" shall be used to disable the keyservers and have dirmngr to return GPG_ERR_NO_KEYSERVER.
Revisions and Commits
|rG936954a18a2d dirmngr: Relax the detection of the "none" keyserver.|
|rG4fc745bc43a7 dirmngr: Relax the detection of the "none" keyserver.|
|rG0aa32e2429bb dirmngr: Allow conf files to disable default keyservers.|
|rG0ad13023905d dirmngr: Allow conf files to disable default keyservers.|
Note that for vsd we also need to change our default configuration file. The new "none" value provides a better error message than the old default of assuming that the AD carries the keyserver (which it does not in practise).
BTW, with one of the recent gpgme fixes we now get
$~/b/gpgme/tests/run-keylist --extern --verbose foo run-keylist: file /home/wk/s/gpgme/tests/run-keylist.c line 414: <Dirmngr> No keyserver available
which is what users (and kleopatra) expects.
This works insofar that it is now possible to set "none" (via the registry in VSD):
But it does not speed up the lookup in Kleopatra as much as hoped for, yet, as we are held up by the error message "Suche auf Zertifikatserver fehlgeschlagen. Die Fehlermeldung lautet:
Kein Schlüsselserver verfügbar":
If we explicitly set "none" as a keyserver, there should be no error message because of it.
Only after acknowledging this message window do we get the WKD result.
I additionally suggest showing the WKD result first and only then showing an info window similar to the one we now show for key updates (T5903). This would fit into the scope of Ticket T6493, "Improvements on search window", though. Please consider to raise the prio of it if you want to continue this issue there.