[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#61792: marked as done (telnet: Can't type non-ascii chars.)

>>>>> "Herbert" == Herbert Xu <herbert@gondor.apana.org.au> writes:

    >> use of 8 bit seems to be all right in most circumstances, and
    >> essential in others, doesn't it make sense to make 8 bit the
    >> default as long as there's a way to override that?

    Herbert> If it didn't brake systems like Solaris 7 or RedHat 6.1,
    Herbert> I would've done that.  -- Debian GNU/Linux 2.1 is out! (
    Herbert> http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~}
    Herbert> <herbert@gondor.apana.org.au> Home Page:
    Herbert> http://gondor.apana.org.au/~herbert/ PGP Key:
    Herbert> http://gondor.apana.org.au/~herbert/pubkey.txt

So, my reading, is that there are two issues which are being confused:

1. Slink telnet broke RFC standards by not negotiating 8 bit properly,
breaking compatibility with SunOS. This problem has been fixed, and is
no longer an issue. It is not related to the next item in any way.

2. If -8 is used to connect to a Solaris 7 system or Redhat 6.1
system, it won't work. Is this because the remote telnetd breaks the

For those who advocate ssh, current openssh versions do not support
Kerberos (not that I am concerned with non-ASCII characters myself).

Disclaimer: I may have lost the plot...
Brian May <bam@debian.org>

Reply to: