Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!decvax!harpo!floyd!clyde!akgua!psuvax!burdvax!presby!seismo!hao!hplabs!sri-unix!lwa@mit-csr
From: lwa%mit-csr@sri-unix.UUCP
Newsgroups: net.unix-wizards
Subject: User Telnet doesn't do netascii properly
Message-ID: <14016@sri-arpa.UUCP>
Date: Wed, 23-Nov-83 14:15:00 EST
Article-I.D.: sri-arpa.14016
Posted: Wed Nov 23 14:15:00 1983
Date-Received: Tue, 29-Nov-83 06:15:45 EST
Lines: 24

Index:    /usr/src/ucb/telnet.c 4.2BSD

Description:
          User Telnet does not properly perform the netascii conversion on
          data being transmitted.  In particular, it sends the carriage
          return character alone without a following newline.  The consensus
          among the Telnet implementers (including Jon Postel) is that
          <CR> should always be followed by <LF>.  The result of this omission
          is that certain hosts drop the first character typed after a <CR>.
Repeat-By:
          Try telnetting to a host whose server Telnet is known to ignore the
          next character sent after a <CR>.
Fix:
          In the routine telnet(), after the lines:

                              if (c == IAC)
                                        *nfrontp++ = c;
                              *nfrontp++ = c;

          add the two lines:

                              if (c == '\r')
                                        *nfrontp++ = '\n';
-------