You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rust port: wss:// dial panics on Linux (no process-level rustls CryptoProvider) #66
Found while writing the conformance negatives in #62 (refs #24).
In poc/reverse-attach-linux, a reverse-attach dial to a wss:// runtime panics inside tungstenite::connect: rustls has no process-level CryptoProvider installed, so TLS setup panics instead of returning an error. A wss:// runtime would therefore panic the dial thread rather than end the grant with a TLS error.
The test attach::client::tests::wss_to_a_plaintext_listener_fails_without_falling_back currently accepts that panic as a failed dial, so it proves only that no plaintext HTTP is sent, not that TLS is attempted.
Fix candidates: install a default provider at startup (rustls::crypto::ring::default_provider().install_default() or the aws-lc equivalent), or enable exactly one rustls crypto feature so the default is picked automatically. Then tighten the test to require a TLS error, not a panic, and add the successful-wss handshake row in docs/parity-checklist.md once a TLS fixture exists.
Labelled p2. Confirmed by reading the code: poc/reverse-attach-linux installs no rustls CryptoProvider and Cargo.lock enables neither the ring nor the aws-lc-rs feature of rustls, while README.md says wss dial works. It is off the default ws:// path, so p2 rather than p1. Suggested fix: add rustls with the ring feature and call install_default() in main() (and once in tests), make the wss test require a TLS/IO error instead of accepting a panic, and correct the README and the parity-checklist row. This unblocks the wss rows from #24 and item 6 of #32.
Activity
test(conformance): address round-1 review of #62 (refs #24)
test(conformance): wire MCP fixtures, reverse-attach negatives, parit…
fix(linux): answer runtime pings during long tool calls (liveness) (#72)
chaodu-agent commentedon Nov 7, 2026
Labelled p2. Confirmed by reading the code:
poc/reverse-attach-linuxinstalls no rustls CryptoProvider andCargo.lockenables neither theringnor theaws-lc-rsfeature of rustls, whileREADME.mdsays wss dial works. It is off the defaultws://path, so p2 rather than p1. Suggested fix: addrustlswith theringfeature and callinstall_default()inmain()(and once in tests), make the wss test require a TLS/IO error instead of accepting a panic, and correct the README and the parity-checklist row. This unblocks the wss rows from #24 and item 6 of #32.test(linux): bound the dial_loop TLS test; drop lab details from the …
feat(linux): in-process JPEG for screenshot, with region and the Swif…
feat(linux): background jobs exec_start/exec_poll/exec_list/exec_canc…