Bug 1116

Summary: Solaris 10: mucho remote terminal problems
Product: Portable OpenSSH Reporter: Jeff Earickson <jaearick>
Component: sshAssignee: Assigned to nobody <unassigned-bugs>
Status: CLOSED WORKSFORME    
Severity: major CC: djm, jaearick
Priority: P2    
Version: 4.2p1   
Hardware: SPARC   
OS: Solaris   

Description Jeff Earickson 2005-11-09 02:32:39 AEDT 
four systems running Solaris 10 on sparc, all have the same problems.  Using openssh4.2p1, OpenSSL 0.9.8a, both ssl and ssh built with Sun's Studio10 compiler (cc, Sun C 5.7 2005/01/07).

The problems have manifested themselves on remote ssh connections from Mac OS 10.4.3 systems using
Mac terminal (version 1.5 build 133) with term definitions xterm, xtermc, xterm-color; and on Win XP
systems using SSH client from www.ssh.com, term definition vt100.  Example: open MacOS terminal with
termdef xterm-color, ssh to the Solaris 10 system, login.  The remote Solaris 10 system uses xtermc for
xterm-color, by way of a symlink in /usr/share/lib/terminfo/x xterm-color->xtermc.  The problems are:

a) a control-C hangs the remote login session.
b) /usr/bin/vi (Sun) or vim (6.4) do not use the full window size but think the window is 80x24.  In my
case I use 80x45.  Doing /usr/openwin/bin/resize gives the right window size, but vi won't work right.
c) /usr/bin/vi with vt100 on XP does not do linewraps correctly.  vim works correctly on XP.
d) After a vi session, if you cat a file then it fills the screen until the bottom.  Then the screen does not
scroll, just all subsequent output goes to the bottom line of the screen.  A "clear" fixes this.

I opened a bug with Sun on this, thinking it was a shell/terminfo problem.  When the guy had me try
all of this with telnet, everything worked perfectly.  The Sun guy said that they have a lot of open bug
reports against their version of ssh just like mine.  But they could not help me with OpenSSH.
Comment 1 Damien Miller 2005-11-09 08:20:36 AEDT 
Do you have similar problems with a different client, like OpenSSH/cygwin or PuTTY?
Comment 2 Damien Miller 2005-12-27 10:36:28 AEDT 
No reply == no bug
Comment 3 Jeff Earickson 2006-01-03 06:12:50 AEDT 
Sorry I dropped the ball on the initial query of 11/09/2005.  I started trying to get things to work with 
cygwin on Solaris 10, discovered I didn't have a cygwin term type with S10.  So, I installed GNU ncurses
which comes with a gob of term types, frigged extensively with my TERMINFO and login settings, etc,
and forgot to answer your question.

Even after using GNU terminfo definitions for xterm and xterm-color on the S10 box, when connected via
a Mac OS X terminal connection, I still have the problems listed in the bug report.  If I ssh from a Windows
2003 server cmd window to the S10 box (thus getting cygwin termtype on the Solaris box) then things
work correctly.

Does this suggest a bug in Solaris 10, somewhere in ther term definitions for xterm?
Comment 4 Damien Miller 2006-03-12 15:51:20 AEDT 
Yes, it does - I have problems with Sol10's terminal definitions too (arrow keys in vi don't work). This probably isn't an OpenSSH bug.
Comment 5 Jeff Earickson 2006-03-15 03:40:15 AEDT 
(In reply to comment #4)
> Yes, it does - I have problems with Sol10's terminal definitions too (arrow
> keys in vi don't work). This probably isn't an OpenSSH bug.
> 

I'm not convinced.  I removed OpenSSH from my Solaris 10 systems, installed Sun's
version of SSH, and all of my ssh related terminal issues vanished.  At this point,
I'm going to with Sun's version.  Arrow keys in vi?  They are h, j, k, and l for me.
I've been using vi since *before* there were arrow keys!  Deal with this bug/non-bug
as you see fit.
Comment 6 Damien Miller 2021-04-23 15:04:33 AEST 
closing resolved bugs as of 8.6p1 release