From bfbe05b44d191108b7a7375270439f2996a03feb Mon Sep 17 00:00:00 2001 From: bagajjal Date: Mon, 13 Mar 2017 19:03:51 -0700 Subject: [PATCH] Updated Terminal Info (markdown) --- Terminal-Info.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Terminal-Info.md b/Terminal-Info.md index 95ffe8f..2080efc 100644 --- a/Terminal-Info.md +++ b/Terminal-Info.md @@ -2,7 +2,7 @@ Windows OS doesn't provide the support for virtual terminal (or) interpret the VT sequences. -As part of the SSH connection establishment, SSH server will create a virtual terminal. SSH Client will transmit each and every keystroke to the virtual terminal at SSH Server. SSH Server virtual terminal will in return sends back the VT sequences to SSH client. Windows SSH client will receive, interpret the VT sequences and renders the data sent by the SSH server. +As part of the SSH connection establishment, SSH server will create a virtual terminal. SSH Client will transmit each and every keystroke to the virtual terminal at SSH Server side. SSH Server virtual terminal will in return sends back the VT sequences to SSH client. Windows SSH client will receive, interpret the VT sequences and renders the data sent by the SSH server. If you are using the openssh client and using the windows cmd.exe/powershell to connect to the SSH server then the cmd.exe/powershell needs to receive, interpret the VT sequences. Unfortunately cmd.exe/powershell doesn't have the ability to interpret the VT sequences until windows 10.