LDAP related stuff.
Details
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.
Fri, Dec 12
setting this to resolved, werner already tested this
Thu, Nov 27
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
Nov 17 2022
Oct 11 2022
Sep 29 2022
Applied and pushed the change from @joeyberkovitz in rG3257385378bb: dirmngr: Interrogate LDAP server when base DN specified..
Sep 26 2022
BTW, I have also in mind to use an AD entry to figure out the used keyserver. It turned out that people don't like to modify the schema of their AD but instead use a separate LDS.
To proceed, I pushed an initial part as rG993820c31521: dirmngr: Factor out interrogate_ldap_dn function., which doesn't change any behavior.
Then, the point of the change will be clearer.
Sep 19 2022
just checking in about getting this patch reviewed
Jul 10 2022
Due to vacation the review may take some time.
Jul 8 2022
Any chance someone is able to review the posted patch?

