LDAP related stuff.
Fri, Mar 17
Mon, Feb 27
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?
Jul 5 2022
Let me know how best to submit it
I tried to submit the below patch to firstname.lastname@example.org, but get an Unrouteable address error. Let me know how best to submit it
Jun 29 2022
The first ideas sounds best to me. Patches please to the mailing list.
Apr 20 2022
Mar 30 2022
Aug 13 2021
Jun 25 2021
This has been solved in 2.2.26 commit rGc75fd75532
Jun 11 2021
May 21 2021
May 19 2021
Having a fallback in Kleopatra makes sense because very old HKP keyservers don't return the fingerprint and LDAP keyservers not using the modernized schema do neither.
I just talked with werner about that and he told me that GnuPG can return the fingerprint. And I also mentioned to him that kleopatra really assumes that a Fingerprint is always set for a valid key object.
Should have linked the commit with a patch for Gpg4win here: 22bc52775bdb I mostly needed that as an immediate fix for someone testing with ldap servers a lot.
Jan 27 2021
Jan 8 2021
The code has been reworked to also support the updated schema which also stores the fingerprints and a parsed down mail address. See gnupg/doc/ldap/ . These changes are in master and 2.2.26. Sorry for taking so long to fix that.
Sep 15 2020
Jul 2 2020
Fixed; In master the code already uses our generic scheme parser.
Nov 26 2019
The LDAP code is actually in very bad shape because @neal added it without utilizing the ldap wrapper and thus a timeout won't work reliable.
Nov 11 2019
See also D475.
May 17 2019
Apr 25 2019
Apr 5 2019
Apr 3 2019
Nov 5 2018
Fixed in master and 2.2.
Oct 25 2018
Oh, that is really old code dating back to dirmngr-1. There is only one user I will see whether I can replace it with the generic parser we have in http.c
Apr 18 2018
Thanks for looking into this issue :-)