Install default rustls crypto provider in each binary - #100
Merged
Merged
Conversation
With both aws-lc-rs and ring providers now linked into rustls 0.23, neither is the process default, causing a panic on first TLS use. Install aws-lc-rs explicitly at the top of each main(), ignoring the result so a second install (e.g. from a library) is a no-op. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 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.
With both aws-lc-rs and ring providers now linked into rustls 0.23, neither is the process default, causing a panic on first TLS use. Install aws-lc-rs explicitly at the top of each main(), ignoring the result so a second install (e.g. from a library) is a no-op.