Enable using MesaLink as an alternative TLS backend #63
Conversation
This file contains 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
Add a new crate feature, `mesalink`, which is passed to the `curl` crate to enable using MesaLink as libcurl's chosen TLS backend. Currently work-in-progress, as we want to wait until the necessary patches are published upstream first. Fixes #22.
sagebind
force-pushed
the
22-mesalink-tls-backend
branch
from
fb8f34b
to
5cc13b3
Compare
|
This is currently blocked by cross-platform concerns. The published MesaLink does not currently support Windows (just landed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a new crate feature,
mesalink, which is passed to thecurlcrate to enable using MesaLink as libcurl's chosen TLS backend.Currently work-in-progress, as we want to wait until the necessary patches are published upstream first.
Fixes #22.