docs: note CURLOPT_PINNEDPUBLICKEY has no effect on legacy LDAP backend#21682
Closed
MegaManSec wants to merge 2 commits into
Closed
docs: note CURLOPT_PINNEDPUBLICKEY has no effect on legacy LDAP backend#21682MegaManSec wants to merge 2 commits into
MegaManSec wants to merge 2 commits into
Conversation
vszakats
approved these changes
May 19, 2026
bagder
approved these changes
May 21, 2026
outcast36
pushed a commit
to greearb/curl
that referenced
this pull request
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The legacy LDAP backend manages TLS through libldap independently of curl's TLS layer, so this option is silently ignored for those connections. The OpenLDAP backend (USE_OPENLDAP) routes TLS through curl's layer and does honor it.