Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!cs.mu.OZ.AU!kre
From: kre@cs.mu.OZ.AU (Robert Elz)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Telnet's ECHO option
Message-ID: <6131@munnari.oz.au>
Date: 29 Nov 90 03:29:56 GMT
References: <gm.3504@ionic.UUCP>
Sender: news@cs.mu.oz.au
Lines: 22

In article <gm.3504@ionic.UUCP>, gm@ionic.UUCP (Greg Miller) writes:
> However, whenever I try this
> when I'm connected to a BSD machine, the host accepts my DONT ECHO,
> replies with WONT ECHO, and then procedes to continue echoing anyways.

There's been a lot of discussion on the nature of DO ECHO / DONT ECHO,
etc, in response to this, but I don't recall much discussion on the
actual problem being reported.

I believe that BSD systems get "DONT ECHO" right, when you ask for them
to not echo, they don't.

But note that "DONT ECHO" is not "DONT OUTPUT" - ie: you still get any
output that processes want to generate (of course).   The perceived
problem is really that some of what seems to be echo is really program
output - it just appears as if it may be echo.

In particular, the "login" program outputs the login name that you enter
(character by character).  This is not "echo", its program output, and
as such, the telnet echo options have nothing to do with it whatever.

kre