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
[Bug] dsh-ssh streams fail on Electron hosts (Desktop app + CLI): BoringSSL has no TLS1.2 PSK ciphersuite — NO_CIPHER_MATCH before any network I/O (EN + 中文全文)
#13190
Community bug report. The repro below needs no container, no plugins, and no DSH session — just node and the Electron binary. Everything was verified on the reporter's machine (see Environment for scope).
Summary
Every dsh-ssh stream connection fails on DSH's Electron hosts — the Desktop app and its CLI carrier — because Electron's node links BoringSSL, which does not implement TLS 1.2 PSK ciphersuites, while the ssh family's stream security pins exactly one:
// packages/ssh/ssh/src/stream-security.ts:7 — identical at 0.2.2-rc.1 and 0.2.2-rc.2ciphers: 'PSK-AES256-GCM-SHA384',minVersion: 'TLSv1.2',maxVersion: 'TLSv1.2',
The failure is thrown during client-side secure-context creation, before any network I/O. The RPC path carries no TLS, so inside a single session the fs tool keeps working while the bash tool cannot open a stream at all.
Reproduction (no container, ~1 minute)
Save this as psk-probe.mjs. The client mirrors the family's authenticateStream() options, including checkServerIdentity: () => undefined (PSK is the authentication):
Start the server with any plain-OpenSSL node — node psk-probe.mjs server — and note the printed port.
Connect with a plain-OpenSSL node: node psk-probe.mjs client <port> → works:
SECURE PSK-AES256-GCM-SHA384
Connect with the Electron binary as node — ELECTRON_RUN_AS_NODE=1 "/Applications/DeepSeek Harness.app/Contents/MacOS/DeepSeek Harness" psk-probe.mjs client <port> → fails before touching the network:
Error: error:100000b1:SSL routines:OPENSSL_internal:NO_CIPHER_MATCH
at configSecureContext (node:internal/tls/secure-context:171:11)
at Object.createSecureContext (node:internal/tls/common:114:3)
at Object.connect (node:internal/tls/wrap:1859:48)
library: 'SSL routines',
function: 'OPENSSL_internal',
reason: 'NO_CIPHER_MATCH',
code: 'ERR_SSL_NO_CIPHER_MATCH'
The Desktop app and its CLI both execute inside the Electron binary with ELECTRON_RUN_AS_NODE=1 (visible in the CLI carrier script), so this is the client runtime every Desktop user gets.
Current behavior
Any connectStream under an Electron host throws NO_CIPHER_MATCH from tls.connect — deterministic, independent of network conditions and of the peer.
In real headless sessions this reproduced 3/3: the bash tool failed with exactly this error while the fs tool (RPC path, no TLS) succeeded in the same session against the same peer.
Present in 0.2.2-rc.1. I unpacked 0.2.2-rc.2's dsh-ssh: the pin is unchanged (same file, same line), so rc.2 is equally affected.
Expected behavior
Either resolution works — the main question is intent:
If the intended client runtime matrix for the ssh family is plain-node only, it would help if Desktop/CLI surfaced a clear precondition error (or fell back to a supported transport) instead of a raw cipher failure.
If Desktop is in scope: a BoringSSL-compatible pin (e.g. a TLS 1.3 PSK suite, which BoringSSL does support), a non-Electron sidecar for stream termination, or a flag we're missing would fix it.
Environment
DSH Desktop 0.2.2-rc.1 and 0.2.2-rc.2, macOS arm64 (Apple silicon). Single machine — all reproductions above come from that one machine; the pin is unconditional in the family code, so I expect it to generalize, but that is expectation, not a tested matrix.
Plain-OpenSSL node v24.21.0 — the Desktop install ships one at runtime/primary-runtime/dependencies/node; under it, family streams verify end-to-end, including full process.prepare → connectStream → process.start → process.wait cycles.
The peer in the in-session reproductions was sshd in a Debian 12 container — irrelevant to the bug, since step 4 fails with no peer contacted at all.
Workaround for anyone hitting this
Launch the headless CLI with the shipped plain-OpenSSL node instead of the Electron carrier; streams work completely. A recipe is documented here: dsh-container-lifecycle README.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Community bug report. The repro below needs no container, no plugins, and no DSH session — just
nodeand the Electron binary. Everything was verified on the reporter's machine (see Environment for scope).Summary
Every
dsh-sshstream connection fails on DSH's Electron hosts — the Desktop app and its CLI carrier — because Electron's node links BoringSSL, which does not implement TLS 1.2 PSK ciphersuites, while the ssh family's stream security pins exactly one:The failure is thrown during client-side secure-context creation, before any network I/O. The RPC path carries no TLS, so inside a single session the fs tool keeps working while the bash tool cannot open a stream at all.
Reproduction (no container, ~1 minute)
psk-probe.mjs. The client mirrors the family'sauthenticateStream()options, includingcheckServerIdentity: () => undefined(PSK is the authentication):Start the server with any plain-OpenSSL node —
node psk-probe.mjs server— and note the printed port.Connect with a plain-OpenSSL node:
node psk-probe.mjs client <port>→ works:ELECTRON_RUN_AS_NODE=1 "/Applications/DeepSeek Harness.app/Contents/MacOS/DeepSeek Harness" psk-probe.mjs client <port>→ fails before touching the network:The Desktop app and its CLI both execute inside the Electron binary with
ELECTRON_RUN_AS_NODE=1(visible in the CLI carrier script), so this is the client runtime every Desktop user gets.Current behavior
connectStreamunder an Electron host throwsNO_CIPHER_MATCHfromtls.connect— deterministic, independent of network conditions and of the peer.dsh-ssh: the pin is unchanged (same file, same line), so rc.2 is equally affected.Expected behavior
Either resolution works — the main question is intent:
Environment
runtime/primary-runtime/dependencies/node; under it, family streams verify end-to-end, including fullprocess.prepare → connectStream → process.start → process.waitcycles.Workaround for anyone hitting this
Launch the headless CLI with the shipped plain-OpenSSL node instead of the Electron carrier; streams work completely. A recipe is documented here: dsh-container-lifecycle README.
Context
中文全文
社区 bug 报告。下面的复现不需要容器、不需要任何插件、也不需要 DSH 会话——只要一个
node和 Electron 二进制。所有验证均在报告者本机完成(范围见「环境」节)。摘要
在 DSH 的 Electron 宿主(桌面应用及其 CLI 载体)上,
dsh-ssh的流连接全部失败:Electron 的 node 链接的是 BoringSSL,而 BoringSSL 未实现 TLS 1.2 PSK 密码套件;ssh 系列包的流安全恰好只锁定这一种:失败发生在客户端安全上下文创建阶段,先于任何网络 I/O。RPC 路径不含 TLS,所以同一个会话里 fs 工具一切正常,而 bash 工具完全打不开流。
复现(无需容器,约 1 分钟)
psk-probe.mjs。客户端完整镜像了系列包authenticateStream()的选项,包括checkServerIdentity: () => undefined(PSK 本身即认证):用任意纯 OpenSSL node 起服务端——
node psk-probe.mjs server——记下打印的端口。用纯 OpenSSL node 连接:
node psk-probe.mjs client <port>→ 成功:ELECTRON_RUN_AS_NODE=1 "/Applications/DeepSeek Harness.app/Contents/MacOS/DeepSeek Harness" psk-probe.mjs client <port>→ 未接触网络即失败:桌面应用与其 CLI 都以
ELECTRON_RUN_AS_NODE=1运行在 Electron 二进制内(CLI 载体脚本可见),所以这就是每个桌面用户实际拿到的客户端运行时。实际行为
connectStream都在tls.connect抛出NO_CIPHER_MATCH——确定性失败,与网络状况和对端无关。dsh-ssh后确认:锁定未变(同文件同行),rc.2 同样受影响。预期行为
两种解决方向都可以——核心问题是意图:
环境
runtime/primary-runtime/dependencies/node);在其下系列包流全链验证通过,包括完整process.prepare → connectStream → process.start → process.wait周期。临时绕行
用桌面自带的纯 OpenSSL node(而非 Electron 载体)启动 headless CLI,流完全可用。配方文档化在此:dsh-container-lifecycle README。
背景
All reactions