LDAP related stuff.
Details
Tue, Jan 13
Fri, Jan 9
The behaviour might have changed a bit because of the ldap: prefix i use now, or i have missed this case the last time:
Given some cert on the "download" server, I can find it, if dirmngr.conf contains only the "download" server, or if the "download" server is listed first:
Independent of keyserver order in dirmngr.conf, --search-keys still offers keys from the upload server, but the download fails:
For "Although the upload server is used for upload, the gpg message still displays the first keyserver" see T8025
Tue, Jan 6
Looks good to me on gpg4win-5.0.0-beta479 @ win11.
Thu, Dec 18
@timegrid I would not tag this ticket with LDAP, as it is not LDAP specific
State in Gpg4win-5.0.0-beta446 and vsd 3.3.4 is this:
So the message is "Update Failed" for keyserver and "not found" for WKD.
In light of that the ticket is this old, I'll leave it at that instead of discussing further improvements beyond this single phrase.
These would have to go in a new ticket.
Dec 12 2025
setting this to resolved, werner already tested this
Nov 27 2025
Tested on gpg4win-5.0.0-beta413 @ win11 with the following entries in dirmngr.conf:
Nov 21 2025
Oct 23 2025
Oct 22 2025
Oct 21 2025
Implemented but not tested at all.
Sep 24 2025
Sep 2 2025
Aug 4 2025
The advantage of using a fingerprint for referencing a key is that there won't be any collisions in the keyid. Further this unifies the schema with an LDS (Windows) installation where DNs must anyway be unique. But take care the client needs to support this new flag. This will be the case for gnupg >= 2.5.12 (cf. T7756)
Jul 25 2025
Oct 9 2024
May 27 2024
Also required for an actium feature with UI.
Sep 25 2023
Actually, a GUI to maintain the keys in an LDAP would be helpful for many sites.
Apr 21 2023
Apr 19 2023
Apr 12 2023
Mar 17 2023
Feb 27 2023
The code has meanwhile been reworked and the mentioned test server is not anymore available

