Bug 2843

Summary:	Control Keys (UP/Down) is not properly working.
Product:	Portable OpenSSH	Reporter:	Rashmi <rashmi.k.agrawal>
Component:	sshd	Assignee:	Assigned to nobody <unassigned-bugs>
Status:	CLOSED WORKSFORME
Severity:	major	CC:	djm, dtucker
Priority:	P5
Version:	5.1p1
Hardware:	Other
OS:	Linux

Description Rashmi 2018-03-23 21:01:12 AEDT

We are usinh Openssh version 5.1. And we are trying to telnet anoth machine through SSH Session logged in with openssh. 

So, while pressing down arrow key to browse the menu resulting into logging out of the telnet session. As OpenSSH sends ESC char on pressing down arrow key first time.

Please let me know if this has been fixed in later version or any other solution for this.

Comment 1 Darren Tucker 2018-03-23 21:31:25 AEDT

(In reply to Rashmi from comment #0)
> So, while pressing down arrow key to browse the menu resulting into
> logging out of the telnet session. As OpenSSH sends ESC char on
> pressing down arrow key first time.

I suspect you have your $TERM set wrong on either the client or on the server after you log in.  What distro is this, which terminal are you using and what is $TERM set to.

Comment 2 Rashmi 2018-03-23 22:18:55 AEDT

Thanks for your reply. Actually we are using openssh source code integrated with my project which runs on linux platform. 

Please find the $TERM output below:

root:/# echo $TERM
vt100

Comment 3 Darren Tucker 2018-04-02 09:42:06 AEST

(In reply to Rashmi from comment #2)
> Thanks for your reply. Actually we are using openssh source code
> integrated with my project which runs on linux platform. 
> 
> Please find the $TERM output below:
> 
> root:/# echo $TERM
> vt100

You didn't answer the question about which terminal emulator you're using, unless you are using a physical VT100, which seems pretty unlikely.

Please fully describe:
 - client including ssh client and terminal emulator
 - server including OS and ssh server.  If this is a self-made OS then debugging that is out of the scope of the OpenSSH team (I'd suggest making sure you have the correct termcap and/or terminfo entries).

Also, 5.1 is pushing 10 years old at this point and has a number of known security issues (see https://www.openssh.com/releasenotes.html and search for "Security").

Comment 4 Damien Miller 2018-07-31 12:00:59 AEST

Closing (three months with no followup from requestor)

Comment 5 Damien Miller 2018-10-19 17:17:27 AEDT

Close RESOLVED bugs with the release of openssh-8.0