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
fix(web): use %USERPROFILE% (not $HOME) in generated Windows ssh commands
The wizard generated Windows ssh commands with a PowerShell-style $HOME in the
identity-file path (e.g. `ssh -i $HOME\.ssh\acfs_ed25519 ...`). In the Windows
Terminal profile `commandline` context (and cmd.exe), $HOME is not expanded
before ssh launches, so OpenSSH gets the literal path, can't find the key, and
falls back to password auth:
Warning: Identity file $HOME\.ssh\acfs_ed25519 not accessible: ...
Switched to %USERPROFILE%, which Windows expands in these contexts (and which the
windows-terminal-setup page already uses for the starting directory). Fixed at
the shared source (commandBuilder SSH_KEY_PATH_WINDOWS) plus the per-page
hardcoded literals across the wizard and the troubleshooting snippets, and
updated the commandBuilder unit test.
Left the genuine PowerShell snippets in generate-ssh-key (Test-Path/New-Item/
ssh-keygen) on $HOME, where interactive PowerShell does expand it correctly.
Closes#302
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments