openssh unix dev - Aug 2020 - OpenSSH 8.3p1 on Fedora 1

I'm not sure if the compat team is interested in this...

I build OpenSSH on antique systems for regression testing, like Fedora
1 and Ubuntu 4. On Fedora 1 this is observed (Ubuntu 4 is OK):

   $ ssh 172.16.4.138
   Last login: Sun Aug  9 23:39:18 2020 from 172.16.2.10
   unknown terminal "xterm-256color"
   unknown terminal "xterm-256color"

I'm not sure where xterm-256color comes from, but it seems to be
specific to Fedora 1. The only mention I can find of it is:

    $ sudo grep -IR xterm-256color /etc
    /etc/termcap:#    * add xterm-88color and xterm-256color -TD

My .bashrc and .bash_profile both exports XTERM=xterm, so it may be
something related to the antique SSH config files. Even though I am
running OpenSSH 8.3, config still comes from the original F1 files. It
may be one of the old F1 settings.

Jeff

On Mon, 10 Aug 2020 at 10:04, Jeffrey Walton <noloader at gmail.com>
wrote:
> I'm not sure if the compat team is interested in this...
>
> I build OpenSSH on antique systems for regression testing, like Fedora
> 1 and Ubuntu 4.
I think I could out-antique that :-)  The general rule is that we'll
support something as long as someone is willing to do the work, and
that it does not compromise support for modern platforms.
> On Fedora 1 this is observed (Ubuntu 4 is OK):
>
>    $ ssh 172.16.4.138
>    Last login: Sun Aug  9 23:39:18 2020 from 172.16.2.10
>    unknown terminal "xterm-256color"
>    unknown terminal "xterm-256color"
Usually that comes from the client's $TERM.   If you do "TERM=vt100
ssh 172.16.4.138" does it go away?

--
Darren Tucker (dtucker at dtucker.net)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.