fix(buzz-pairing-cli): install rustls crypto provider before wss:// use - #4153
Open
jlove2177-jpg wants to merge 1 commit into
Open
fix(buzz-pairing-cli): install rustls crypto provider before wss:// use#4153jlove2177-jpg wants to merge 1 commit into
jlove2177-jpg wants to merge 1 commit into
Conversation
buzz-pair crashed with "Could not automatically determine the process-level CryptoProvider" on any wss:// relay — tokio-tungstenite's rustls-tls-webpki-roots feature needs a provider installed explicitly, which every other binary in the workspace already does (buzz-relay, buzz-desktop) but this one never did. Only surfaced when actually testing wss:// interop, since ws:// never touches TLS. Signed-off-by: Eldritch Architect <jlove217@gmail.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
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.
Summary
buzz-pair(the NIP-AB pairing interop CLI) panicked withCould not automatically determine the process-level CryptoProvideron anywss://relay —tokio-tungstenite'srustls-tls-webpki-rootsfeature needs a provider installed explicitly. Every other binary in the workspace that touches TLS (buzz-relay,buzz-desktop) already does this;buzz-pairing-clinever did.wss://, sincews://never touches TLS — easy to miss since the tool defaults to awss://public relay but most local dev/testing uses plainws://.Test plan
cargo build -p buzz-pairing-clibuzz-pair source --relay wss://<host>andbuzz-pair targetagainst a real TLS-terminated relay — connects and proceeds past the crash point (reaches SAS exchange) instead of panicking immediately.