Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: legacy ldap?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 3 Dec 2025 13:15:16 +0100 (CET)
On Wed, 3 Dec 2025, Patrick Monnerat wrote:
> Removal of ldap.c would mean: "use openldap or be 100% compatible or die".
Sure. But if nobody uses it, there are no casualties only winners.
Note though that I do not actually suggest we remove it at this point. As a
starter, I'm trying to learn if there are anyone who cares.
(So far not a single person has said they do.)
There are some recently reported and still undisclosed problems with the
ldap.c code and the general (non-OpenLDAP) LDAP API that I'm wrestling with
and I try to assess the impact and size of these problems. It might affect how
we decide to act.
Date: Wed, 3 Dec 2025 13:15:16 +0100 (CET)
On Wed, 3 Dec 2025, Patrick Monnerat wrote:
> Removal of ldap.c would mean: "use openldap or be 100% compatible or die".
Sure. But if nobody uses it, there are no casualties only winners.
Note though that I do not actually suggest we remove it at this point. As a
starter, I'm trying to learn if there are anyone who cares.
(So far not a single person has said they do.)
There are some recently reported and still undisclosed problems with the
ldap.c code and the general (non-OpenLDAP) LDAP API that I'm wrestling with
and I try to assess the impact and size of these problems. It might affect how
we decide to act.
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-12-03