[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.)

On Tue, Apr 11, 2000 at 09:34:34PM +1000, Herbert Xu wrote:
> On Tue, Apr 11, 2000 at 12:17:38PM +0200, Richard Braakman wrote:
> > On Tue, Apr 11, 2000 at 07:15:02PM +1000, Herbert Xu wrote:
> > > 
> > > Unfortunately AFAIK there isn't an RFC specifying the BINARY option.
> > 
> > RFC 856, Telnet Binary Transmission. (Status: STANDARD)
> I stand corrected.  But it doesn't really solve the problem because there is
> no mention about \r\n conversions which seems to be the problem here.

That's in section 3.2.7 of RFC 1123 :-)

         When the Binary option has been successfully negotiated,
         arbitrary 8-bit characters are allowed.  However, the data
         stream MUST still be scanned for IAC characters, any embedded
         Telnet commands MUST be obeyed, and data bytes equal to IAC
         MUST be doubled.  Other character processing (e.g., replacing
         CR by CR NUL or by CR LF) MUST NOT be done.  In particular,
         there is no end-of-line convention (see Section 3.3.1) in
         binary mode.

I'm guessing that one or both sides is attempting to abuse the BINARY
mode as an "8-bit terminal" mode.  Section 3.2.5 discusses that.  
In particular, it sort-of blesses the use of 8-bit characters in
the normal terminal mode.

> In any case, Solaris 7 and RedHat 6.1 is out of our control so AFAIC the
> current settings is gonig to stay.

Is our side well-behaved, though?

Richard Braakman
(wrote a telnetd implementation once)

Reply to: