Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!cbmvax!vu-vlsi!mpx1!erik
From: erik@mpx1.UUCP (Erik Murrey)
Newsgroups: comp.mail.uucp
Subject: Re: uucp via a rlogin session
Summary: escape sequences
Message-ID: <545@mpx1.UUCP>
Date: 2 Oct 88 21:07:49 GMT
References: <531@comdesign.CDI.COM> <317@magnus.UUCP> <13797@mimsy.UUCP> <13811@mimsy.UUCP>
Distribution: na
Organization: MPX Data Systems, Inc.,  Wayne,  Pennsylvania
Lines: 24

In article <13811@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) writes:
> As long as UUCP never transmits one of the sequences
> 
> 	RETURN escchar .
> 	RETURN escchar Meta-DEL
> 	RETURN escchar escchar
> 
> (where escchar is the character set by -e, default `~') it will
> continue to work.  Obviously, these three sequences are statistically
> unlikely: P=3/256^3 in uniformly random data, or about .000018%.  You

The escape sequence for TELENET (not telnet) is <cr>@<cr>.  I found
that when transmitting compressed files over PC-Pursuit, the file
almost always contained this escape sequence, which escaped out of
PC-Pursuit and caused the transmission to fail.  I think that compressed
files contain a very random distribution of the entire 8 bit set.
(This is why compresseing a compressed file makes an even bigger file,
right?) I would think that you would hit the rlogin escape very easily when
sending 14 or 16 bit compressed files.
-- 
Erik Murrey                            /|   //  /~~~~/  |  /
MPX Data Systems, Inc.                / | / /  /____/   |/
erik@mpx1.UUCP                       /  /  /  /        /|  Data Systems, Inc. 
{spl1,vu-vlsi,bpa}!mpx1!erik        /     /  /       /  |====================