tyler.durden/Win32-OpenSSH
1
0
Fork 0
mirror of https://github.com/PowerShell/Win32-OpenSSH.git synced 2025-07-26 07:25:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

Halfway through an edit pass

Joey Aiello 2017-05-17 16:01:45 -07:00
parent 653c0b3a9c
commit 202db53914
1 changed files with 35 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
TTY-PTY-support-in-Windows-OpenSSH.md

@ -1,25 +1,45 @@
# SETUP # SETUP
## Windows SSH Client to UNIX SSH server ## Windows SSH client to Linux/Unix/macOS (*nix) SSH server
If you want to use vi / top / man, etc commands while connecting from windows client to Linux server then please follow these steps
If you want to have the best experience while using utilities like vi, top, man, etc. while connected from a Windows SSH client to a *nix server, you should configure your terminal to use an xterm-like rendering mode.
1) Upgrade to windows 10+ OS. Unfortunately, this rendering mode is only included with Windows 10. If you're not on Windows 10, you may have more luck using a third-party terminal emulator or console host like [Cmder]() or [ConEmu]().
2) Set the non-legacy console mode in the console properties, 1. Open a shell from which you want to use `ssh` (either `powershell` or `cmd`).
Make sure you **uncheck** the "use legacy console" 1. Right-click the application icon in the upper-left and the window and select `Properties`.
![image](https://cloud.githubusercontent.com/assets/23668037/23882278/cc062726-081c-11e7-8e4c-792da6af23b9.png) 1. Ensure that `Use legacy console (requires relaunch)` is unchecked:
3) Set the Screenbuffer width, window size width to >= 90. ![image](https://cloud.githubusercontent.com/assets/23668037/23882278/cc062726-081c-11e7-8e4c-792da6af23b9.png)
![image](https://cloud.githubusercontent.com/assets/23668037/23882328/11ed4116-081d-11e7-87e0-757680ea3a74.png) 1. In the `Layout` tab, set the Screen Buffer width and Window Size width to >= 90:
4) Set the environment variable (TERM) to xterm. Before logging into the SSH server. ![image](https://cloud.githubusercontent.com/assets/23668037/23882328/11ed4116-081d-11e7-87e0-757680ea3a74.png)
c:\test\> set TERM=xterm
c:\test\> set TERM (This should show the term set to xterm)
## UNIX SSH Client to WINDOWS SSH server All of these changes will persist within the same shortcut to `cmd` or `powershell`.
1) Set the environment variable (TERM) to xterm. Before logging into the SSH server. If you want to change the defaults for *new* shortcuts, select `Defaults` in Step 2 instead of `Properties`.
![image](https://cloud.githubusercontent.com/assets/23668037/25919629/1790cfcc-3584-11e7-954c-d3df3c86f8ec.png) 1. Set the `TERM` environment variable to `xterm`:
```
set TERM=xterm
```
In PowerShell you can also use the `$env:` namespace to edit this variable:
```powershell
$env:TERM = 'xterm'
```
Both of these methods will only persist for the current session.
If you want this to happen every time you start PowerShell, you can leverage [PowerShell profiles]().
## Linux/Unix/macOS SSH client to Windows SSH server
1. Set the `TERM` environment variable to `xterm`:
```bash
export TERM=xterm
```
## Windows SSH Client to Windows SSH server
## WINDOWS SSH Client to WINDOWS SSH server
1) Set the non-legacy console mode in the console properties, 1) Set the non-legacy console mode in the console properties,
Make sure you **uncheck** the "use legacy console" Make sure you **uncheck** the "use legacy console"
![image](https://cloud.githubusercontent.com/assets/23668037/23882278/cc062726-081c-11e7-8e4c-792da6af23b9.png) ![image](https://cloud.githubusercontent.com/assets/23668037/23882278/cc062726-081c-11e7-8e4c-792da6af23b9.png)