Explain Windows SSH shell selection

This commit is contained in:
Dandaedre 2026-10-17 09:32:47 +02:00
parent 3522f87dea
commit 4c38825b20
2 changed files with 8 additions and 1 deletions

View File

@ -140,6 +140,8 @@ cc menu # optional numbered menu
For a two-command temporary debugging shell, or for permanent key-based access
from CachyOS, follow the
[advanced remote access guide](docs/advanced-remote-access.md#quick-temporary-access).
The temporary helper prints an SSH command that opens PowerShell directly;
ordinary Windows SSH sessions open `cmd.exe`, which does not recognize `irm`.
`sync` refuses to run while the checkout has uncommitted or untracked files. It
does not reset the checkout. Commit your edits first, or remove files you did not

View File

@ -26,7 +26,7 @@ to Private networks and the local subnet. It then prints the exact second
command to run from CachyOS, for example:
```bash
ssh Alice@192.168.1.42
ssh -t Alice@192.168.1.42 powershell.exe -NoLogo -NoProfile
```
Sign in with the Windows account password. A Windows Hello PIN cannot
@ -34,6 +34,11 @@ authenticate an SSH connection. If the helper reports that no Private network
is active, change the trusted LAN's Windows network profile to Private before
connecting; it deliberately leaves SSH unreachable on Public networks.
A plain `ssh Alice@192.168.1.42` login normally opens `cmd.exe`, where
PowerShell aliases such as `irm` are not available. Type `powershell.exe` in an
existing session to switch shells, or use the command above to enter PowerShell
directly.
When debugging is finished, run this from Windows PowerShell, locally or through
the SSH shell: