Skip to content

Select Rustls provider in Buzz CLI#2530

Closed
colinmarsch wants to merge 1 commit into
block:mainfrom
colinmarsch:cmarsch/fix-cli-rustls-provider
Closed

Select Rustls provider in Buzz CLI#2530
colinmarsch wants to merge 1 commit into
block:mainfrom
colinmarsch:cmarsch/fix-cli-rustls-provider

Conversation

@colinmarsch

Copy link
Copy Markdown

Why

When buzz-cli is built alongside workspace crates that enable Rustls's other crypto backend, both providers are compiled and Rustls panics before the first secure WebSocket connection because it cannot select one automatically.

What

  • Select the ring CryptoProvider explicitly at CLI startup
  • Add a startup regression test that verifies a provider is installed before WebSocket setup

Risk Assessment

Low — this only makes the CLI's TLS provider selection deterministic and matches the provider already selected by other Buzz binaries.

References

  • cargo test -p buzz-cli — 251 tests passed
  • CMAKE_POLICY_VERSION_MINIMUM=3.5 cargo build --release -p buzz-acp -p buzz-agent -p buzz-dev-mcp -p git-credential-nostr -p buzz-cli — exact combined sidecar build passed

Generated with Codex

Combined sidecar release builds enable both Rustls backends, so auto-selection panics before a secure WebSocket connection. Install the ring provider explicitly at CLI startup.

Co-authored-by: Colin Marsch <cmarsch@squareup.com>
Signed-off-by: Colin Marsch <cmarsch@squareup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant