From am@amsoft.ru  Thu Oct 30 12:37:14 1997
Received: from amsoft.ru (amsoft.ru [194.87.86.241])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA08260
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 30 Oct 1997 12:34:26 -0800 (PST)
          (envelope-from am@amsoft.ru)
Received: (from am@localhost) by amsoft.ru (8.8.5/amsoft/1.0)
	id XAA01169 ; Thu, 30 Oct 1997 23:20:24 +0300 (MSK)
Message-Id: <199710302020.XAA01169@amsoft.ru>
Date: Thu, 30 Oct 1997 23:20:24 +0300 (MSK)
From: Andrew Maltsev <am@amsoft.ru>
Reply-To: am@amsoft.ru
To: FreeBSD-gnats-submit@freebsd.org
Subject: Telnet is not transparent with -8E
X-Send-Pr-Version: 3.2

>Number:         4899
>Category:       bin
>Synopsis:       Telnet is not transparent even with -8E
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 30 12:40:03 PST 1997
>Closed-Date:    Thu Jun 4 20:45:02 PDT 1998
>Last-Modified:  Thu Jun  4 20:45:53 PDT 1998
>Originator:     Andrew Maltsev
>Release:        FreeBSD 2.2.1-RELEASE i386
>Organization:
AM'SOFT
>Environment:

	

>Description:

 Telnet is not transparent even when it is invoked with -8E swithes. It
 still accepts 0xFF code as an `escape' symbol causing inability to
 transfer binary data over telnet sessions.

 May be it were fixed since 2.2.1 release, excuse me in that case.

>How-To-Repeat:

 Enter 0xFF code in -8E telnet session (and hack your provider :).

>Fix:
	
 Do not tried to fix - just discovered a bug on my home box, but should
 be simple I think..

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Thu Jun 4 20:45:02 PDT 1998 
State-Changed-Why:  
I am unable to repeat this problem and have failed in my 
attempts to contact the originator. 
>Unformatted:
