Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!ucbvax!tut.cis.ohio-state.edu!ukma!rutgers!att!alberta!calgary!xenlink!deraadt
From: deraadt@xenlink.UUCP (Theo A. DeRaadt)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet2.0
Summary: telnet?
Message-ID: <58@xenlink.UUCP>
Date: 7 May 89 09:17:46 GMT
References: <8905070127.AA13702@postgres.Berkeley.EDU>
Organization: Nowhere particular
Lines: 26

In article <8905070127.AA13702@postgres.Berkeley.EDU>, dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
- :[Can be nasty telnetting out.]  Anyhow, I digress.  DNet will not run
- :over telnet, probably because of this point of non-transparency.
- :Unless Matt has specifically changed it for 2.0 [I haven't tried it
- :yet] but I don't think so.  [Matt?]  The other major point of
- :nontransparency in telnet is the escape character, usually ^].  (don't
- :know the character code offhand.)
- :
- :On the other hand, the rlogin protocol IS transparent enough to run
- :dnet over.  If you can use a straight TCP connection or an rlogin
- :connection (which is fairly close) DNet should run fine over it.  With
- :a telnet connection, you can't do much about it.
- 
- 	DNet will not run under telnet for that and other reasons... like
- ^] causes an escape.  DNet *will* run under rlogin because rlogin recognizes
- when a terminal is placed in RAW mode and turns off it's escapes.

If anyone wants a program that will fake the telnet stuff, I have one
for BSD (what? telnet on a non-BSD? :-) that I hacked up one boring
rainy/snowy night.. lemme know if you want source. You will have source,
so you can toast the escape key feature, or I can bind it to a cmdline
option....

Of course, I have an idea that telnet might have an option to turn off
the escape character... never checked.
 <tdr.