Tue, Mar 21
We need to extend dirmngr_ldap.c to take a list of attributes to return. We already have the --multi option which returns all attributes for latter filtering by the caller but the specified attr is also used and thus dirmngr's start_cacert_fetch_ldap() retruns only the requested caCertificate.
Fri, Mar 17
Mon, Feb 27
The code has meanwhile been reworked and the mentioned test server is not anymore available
Jan 19 2023
Dec 5 2022
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 22 2022
Sep 19 2022
What is a partial CRL; I have never seen that and IIRC the specification for that was not complete.
For what it is worth, I think that my patch is more standard compliant then yours because it checks if there is a partial CRL.
I think 289fbc550d18a7f9b26c794a2409ba820811f6b3 implemented this wish from 2016 :) @werner please read the full report and then close it as fixed if you agree. I find it a bit funny that we both came independently to the same conclusion, that it should be handled differently even if the standard says otherwise. Because the behavior from the standard does not make sense and is in contradiction to other parts where it says that each CRL must contain all revocations.
just checking in about getting this patch reviewed
Sep 16 2022
That particular bug seems to have been solved a long time ago. I stumbled upon up while fixing a DP bug today.
Sep 14 2022
Awesome, thanks all! From an end user perspective that would be a perfectly acceptable outcome, the warning just serves to confuse people. Appreciate the help!
I have created the spin-off T6202: Kleopatra: Suppress errors of WKD lookups to deal with not bothering Kleopatra's users with error messages when doing a WKD lookup in the background. This task is for improving dirmngr.
Jul 29 2022
Jul 26 2022
The fix has been merged to the 2.2 branch.
Jul 15 2022
What i don't understand is ...
Jul 10 2022
Due to vacation the review may take some time.
Jul 8 2022
It will hopefully be fixed in 2.2.37.
thanx for fixing this issue ...
Any chance someone is able to review the posted patch?
Jul 7 2022
Jul 5 2022
Let me know how best to submit it
I tried to submit the below patch to email@example.com, 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 28 2022
Apr 25 2022
Was fixed in 2.3.5
Apr 20 2022
Apr 14 2022
We have not seen this problem anymore in recent versions. Thus closing.
We have a solulion for this bug. For further improvements we will use T5882.
Mar 30 2022
Mar 28 2022
Good idea. Thanks. Goes onto 2.3 and 2.2
Mar 25 2022
Confirmed to work, thanks!
it still shows the no certificate or invalid encoded error message:
Mar 24 2022
I gave it a try. It works now, but it still shows the no certificate or invalid encoded error message: