PowerShell / PowerShell/Win32-OpenSSH
ssh get sucked after remotely logging to a Ubuntu
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
I simply launched a windows 10 cmd line.
C:\Users\vanil>ssh
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface]
[-b bind_address] [-c cipher_spec] [-D [bind_address:]port]
[-E log_file] [-e escape_char] [-F configfile] [-I pkcs11]
[-i identity_file] [-J [user@]host[:port]] [-L address]
[-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
[-Q query_option] [-R address] [-S ctl_path] [-W host:port]
[-w local_tun[:remote_tun]] destination [command]
Logged into a Ubuntu workstation remotely from that terminal. The directory of the cmd line is totally messed up:
Last login: Thu Jun 20 18:22:03 2019 from 24.5.30.160
ls
-bash: cd: pls: No such file or directory
ls
aconda3-4.4.0-Linux-x86_64.sh anaconda3 cuda-repo-ubuntu1804_10.0.130-1_amd64.deb pytorch
cd pytorch
cpytorch: command not found
cd pytorch
];alla_att@tesla: /pytorchvanilla_att@tesla:/pytorch$ Connection to 35.227.134.181 closed by remote host.
Connection to 35.227.134.181 closed.
Can anybody please point to a reason and treatment of it? Thanks.
Troubleshooting steps
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting-Steps
Terminal issue? please go through wiki
https://github.com/PowerShell/Win32-OpenSSH/wiki/TTY-PTY-support-in-Windows-OpenSSH
Please answer the following
"OpenSSH for Windows" version
Version 10.0.18362.175
Server OperatingSystem
Ubuntu 18.04.1 LTS
Client OperatingSystem
Version 10.0.18362.175
What is failing
Expected output
vanilla_att@tesla: ~/pytorch$
Actual output

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Troubleshooting Steps and TTY/PTY support wiki pages, then reproduce the session from Windows 10 cmd to Ubuntu 18.04.1 using the reported ssh command. Compare the expected prompt and directory with the corrupted input and connection output; done means identifying a reproducible cause and documenting or fixing the terminal behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100