[Bug]: IdentitiesOnly=yes incorrectly disables SSH agent authentication with a public IdentityFile
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start in pkg/remote/sshclient.go, especially createClientConfig() and createPublicKeyCallback(), which the issue identifies as the agent initialization and identity parsing entry points. Read how configured IdentityFile values and agent keys are handled, then locate the SSH client tests for regression coverage. Done means matching agent keys can authenticate with IdentitiesOnly enabled, while unrelated keys remain excluded; the issue asks for coverage with the setting both enabled and disabled.
由索引模型根據 Issue 內容生成。
描述
Current Behavior
Wave Terminal fails to authenticate using an SSH agent when IdentitiesOnly yes is specified in ~/.ssh/config, even when IdentityFile explicitly identifies a public key whose corresponding private key is available through the agent.
The same configuration works correctly with the native OpenSSH client on Windows.
This appears to be an incompatibility with OpenSSH's documented IdentitiesOnly behavior.
Environment
OS: Windows 11
SSH agent: Bitwarden SSH Agent
SSH client comparison: Windows OpenSSH (ssh.exe)
Wave Terminal version: [insert installed version]
The private key is managed by Bitwarden and is not stored as a local file. The corresponding public key is stored locally.
Expected Behavior
Expected Behavior
According to OpenSSH's ssh_config(5) documentation:
IdentityFile may point to a public key file when the corresponding private key is managed by an SSH agent.
IdentitiesOnly yes restricts authentication to the explicitly configured identities.
It does not disable SSH agent authentication.
The SSH client should request signatures from the agent only for keys matching the configured identities.
Therefore, Wave should successfully authenticate using the matching Bitwarden-managed private key, without trying unrelated identities from the agent.
Actual Behavior
Wave appears to disable SSH agent authentication entirely when IdentitiesOnly yes is enabled, causing authentication to fail because the specified .pub file cannot be used directly as a private key.
Steps To Reproduce
Configure Bitwarden as the system SSH agent and ensure the corresponding key is available through the agent.
Add the following entry to ~/.ssh/config:
Host testserver
HostName 192.0.2.10
User root
IdentityFile C:/path/to/myhome.pub
IdentitiesOnly yes
Replace the example address and public key path with a working SSH server and the appropriate public key.
Run ssh testserver in PowerShell. Authentication succeeds.
Connect to the same host using Wave Terminal's built-in SSH connection. Authentication fails with:
ssh: handshake failed: ssh: unable to authenticate,
attempted methods [none publickey],
no supported methods remain
Comment out IdentitiesOnly yes, without changing anything else, and retry. Both Windows OpenSSH and Wave Terminal now connect successfully.
Wave Version
0.14.5
Platform
Windows 11
OS Version/Distribution
26H2
Architecture
x86_64
Anything else?
Possible Root Cause
In pkg/remote/sshclient.go, createClientConfig() contains:
if !utilfn.SafeDeref(sshKeywords.SshIdentitiesOnly) && agentPath != "" {
conn, err := dialIdentityAgent(agentPath)
// ...
}
This condition skips SSH agent initialization whenever IdentitiesOnly is true.
Additionally, createPublicKeyCallback() attempts to parse configured identity files as private keys using ssh.ParseRawPrivateKey(), without implementing the OpenSSH behavior of matching a public IdentityFile against the keys available from the agent.
Source:
https://github.com/wavetermdev/waveterm/blob/main/pkg/remote/sshclient.go
OpenSSH reference:
https://man.openbsd.org/ssh_config#IdentitiesOnly
Suggested Fix
Allow SSH agent initialization regardless of the IdentitiesOnly setting.
When IdentitiesOnly is true, filter agent-provided identities against the public keys specified by IdentityFile.
Support public-key-only IdentityFile entries, including .pub files, when the associated private key is held by the agent.
Add regression tests covering both IdentitiesOnly yes and no, with and without a matching agent key.
Workaround
Setting IdentitiesOnly no allows Wave to connect successfully.
However, this workaround changes authentication behavior by allowing additional keys from the SSH agent to be attempted. It is not equivalent to the intended OpenSSH behavior.
The issue affects SSH agents that manage private keys externally, including Bitwarden and potentially hardware-backed SSH agents.
- 主要語言
- Go
- 星號
- 22.7k
- 分支
- 1.2k
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
wavetermdev/waveterm 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 66/100
wavetermdev/waveterm#3601 ·
維護者通常 1 天內回覆
-
bug triage
難度 2/5 1-3 小時 新手友好度 67/100
wavetermdev/waveterm#3596 ·
維護者通常 1 天內回覆
-
[Bug]: `wsh termscrollback` returns zero lines for valid ranges starting at line 0可能已有人在做 @bardrop 於 6 天前認領。 未關閉bug triage
難度 2/5 1-3 小時 新手友好度 66/100
wavetermdev/waveterm#3587 ·
維護者通常 1 天內回覆
-
bug triage
難度 2/5 1-3 小時 新手友好度 75/100
wavetermdev/waveterm#3568 ·
維護者通常 1 天內回覆
-
pwsh: encodeEnvVarsForPowerShell rejects Windows-standard env var names like ProgramFiles(x86), breaking wsh token on every pwsh block可能已有人在做 @vortsghost2025 於 72 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 84/100
wavetermdev/waveterm#3481 · 1 則留言 ·
維護者通常 1 天內回覆
查看 wavetermdev/waveterm 的全部 Issue
相似的 Issue
-
good first issue help wanted javascript
難度 2/5 1-3 小時 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 64/100
fullsend-ai/fullsend#9733 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
karmada-io/karmada#8101 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆