From owner-freebsd-net  Sun May 14 10:46:40 2000
Delivered-To: freebsd-net@freebsd.org
Received: from databus.databus.com (databus.databus.com [198.186.154.34])
	by hub.freebsd.org (Postfix) with SMTP id C311637B7F1
	for <freebsd-net@FreeBSD.ORG>; Sun, 14 May 2000 10:46:32 -0700 (PDT)
	(envelope-from barney@databus.databus.com)
From: Barney Wolff <barney@databus.com>
To: freebsd-net@FreeBSD.ORG
Date: Sun, 14 May 2000 13:29 EDT
Subject: Re: socket programming
Content-Length: 1212
Content-Type: text/plain
Message-ID: <391ee6760.158e@databus.databus.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Have you actually tried it, with a real telnet client?

As I understood the question, it was:  How does the server make the
client stop echoing to the user?  And the answer is for the server
to tell the client that it will do the echoing itself, and then
not really do it.

See RFC 857.

Barney

> Date: Sun, 14 May 2000 19:28:30 +0200
> From: Alexander Langer <alex@big.endian.de>
> To: Barney Wolff <barney@databus.com>
> Cc: freebsd-net@FreeBSD.ORG
> Subject: Re: socket programming
> Content-Length: 660
> 
> Thus spake Barney Wolff (barney@databus.com):
> 
> > Well, telnet is a funny protocol.  Both answers have been wrong.
>                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Interesting point. Unfortunately, since the server isn't going to echo
> back the chars, DON'T ECHO has the same effect.
> 
> The difference between DON'T/WILL has effect if you assume, that the
> server echo's back each char it receives. Then client in WILL
> situation will echo, client in DON'T won't echo. But since the server
> won't echo anyways, there's no difference.
> 
> You could have pointed that out without telling us we are wrong, which
> isn't true.
> 
> Alex
> 
> -- 
> I need a new ~/.sig.
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message