Mh, let us concentrate in here on error messages. I was thinking "but what about disable-dirmngr in the settings" then all publish / refresh / receive actions should be disabled or invisible. So that is better something for a different task.

In T6761#179919, @ebo wrote:

This is not as intended. When doing a search, we wanted No error message and only WKD search should be executed.

I haven't touched this code or the error message. All I did is make the function hasKeyserverConfigured() return false if the key server has been disabled explicitly with "none". This does now trigger the error message which wasn't triggered before because gpg always used the default key server if no key server was configured.

Likewise, refresh should then only search for WKD.

I was talking about "Refresh OpenPGP Keys". This functionality has always simply called gpg --refresh-keys which knows nothing about WKD.

Yes, It was not my intention that WKD should not work when searching for keys, when keyserver is None. Although such a search could be handled by just entering the email address in the recipient dialog in the file encryption widget to trigger a locate key or in the case of GpgOL to enter the recipient mail but I think that feature is very hidden / not really discoverable for users. And yes an improvement for the search Window in that case would be to then switch to "Enter Email" and use an email validator on the input field for example. So let us handle this as part of T6493

@ebo Is this fixed now?

@aheinecke For Gpg4win I do not have a suitable test version yet.

In VSD 3.2.0/3.2.1 the fixes from this ticket are not included

For VSD there should at least no info message be shown - which has to be clicked away - when keyserver is set to "None"

I have backported the relevant commits to gpg4win/23.10 for VSD 3.2. I left out the commit that adds a tooltip.

with Version 3.2.2.231170+git~ (Gpg4win-4.3.1-beta12):

• no error message any more with keyserver = none
• correct error message when choosing "publish on server"

But in the case "Refresh OpenPGP keys" (in Kleopatras certificate Details) there is no error message but instead ~"the key is unchanged".

In T6761#183780, @ebo wrote:

But in the case "Refresh OpenPGP keys" (in Kleopatras certificate Details) there is no error message but instead ~"the key is unchanged".

It seems that gpgme doesn't report an error if no keyserver is defined. -> T7036: gpgme: gpgme_op_receive_keys does not return an error if keyserver lookup is disabled

And that Kleopatra attempts a keyserver lookup for keyserver none is handled by T7037: Kleopatra: Handle disabled keyserver when updating a certificate.

Note to self: The error message that nothing was found on the keyserver will still come up if one is configured. That will be fixed with T6493.