Make WebSocket rustls provider selectable - #92
Open
mirsella wants to merge 1 commit into
Open
Conversation
mirsella
force-pushed
the
rustls-provider-selection
branch
from
July 27, 2026 07:59
6216518 to
69d73f2
Compare
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
1 participant
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.
aeronet_websocketcurrently installs AWS-LC when its Bevy plugin is added. That can conflict with applications that already use ring or another rustls provider, since provider selection is process-wide.This keeps AWS-LC as the default but lets applications disable it and install their own provider before building TLS configs. The patch also makes the client/server feature split explicit and adds CI coverage for providerless, ring-only, and mixed-provider setups.