Bug 30046

Summary: telnetd double echo in local echo mode
Product: [Retired] Red Hat Linux Reporter: Thomas J Pinkl <thomas.pinkl>
Component: telnetAssignee: Harald Hoyer <harald>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-08-05 08:16:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas J Pinkl 2001-02-28 18:01:27 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.17-8-HBS i686)


When telnetd is told "DONT ECHO" during Telnet option negotiations,
it appears that the pseudo terminal (pty) is not configured properly.
After a successful login, characters typed at a shell prompt appear 
twice: once from the local Telnet client and once from the shell.
Other Unix operating systems do not exhibit this behavior.  I've 
tested SCO OpenServer 5.0.5 and IBM AIX 4.3.3.

This "double echo" bug is present in Red Hat Linux 6.1 with 
telnet-0.10-31 and in Red Hat Linux 7.0 with telnet-server-0.17-7.


Reproducible: Always
Steps to Reproduce:
1. You need a Telnet client set to echo locally.  It must not allow
   the server to echo.
2. Open a telnet connection to a Linux host.  Enter your username and
   password.  You will see the password as you type it.
3. At the shell prompt, type something like "date".  You will see 
   "ddaattee".
Comment 1 Harald Hoyer 2001-08-01 06:45:38 UTC 
Could you please retry with:
ftp://people.redhat.com/harald/telnet-0.17-16.src.rpm
Bonus: security fixes to the recently discovered vulnerabilities