Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!shelby!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: NeXTStep 2.0 and NCSA Telnet.
Message-ID: <1277@toaster.SFSU.EDU>
Date: 4 Feb 91 08:59:14 GMT
References: <91031.224509PVJQC@CUNYVM.BITNET>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 31

In article <91031.224509PVJQC@CUNYVM.BITNET> PVJQC@CUNYVM.BITNET writes:
>The new telnetd in NextStep 2.0 comes from 4.3-Reno, and seems to be,
>shall we say, too sophisticated for old programs like NCSA Telnet
>(and just about every other telnet in the known universe).

WRONG.  The problem is unique to the IBM PC (you actually have an
early Clarkson release, not an NCSA release).  It's a bug which
is not present in the current Clarkson or NCSA releases--or any
other implementation or PC telnet I've tried, nor does it affect
NCSA Telnet for the Macintosh or its derivatives.

>                                                           To fix the
>problem, you have to replace the new telnetd with the old one from
>1.0.

That one is broken, broken, broken.  That's why we flushed it
as soon as we could.

I'm aware of *five* public releases of BSD telnetd newer than
what was shipped with 1.0:

[NeXT 1.0]	5/12/86
4.3-tahoe(?)	2/23/89
telnet.90.03.01	3/ 1/90
telnet.90.06.28	6/28/90 <- your telnet broke here
4.3-reno 	6/30/90
telnet.90.09.14	9/14/90

BTW, I *don't* recommend the 90.09.14 telnetd, just its telnet.

					-=EPS=-