Bug 111626

Summary: telnet 0 fails with latest glibc
Product: [Retired] Red Hat Linux Reporter: Abel Lopez <alop>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-26 04:48:29 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 Abel Lopez 2003-12-06 20:13:13 UTC 
Description of problem:
on systems with glibc-2.2.93-5, you can connect to localhost by typing
'telnet 0 [port]'
on systems with glibc-2.3.2-4.80.6, typing telnet 0 returns
telnet: 0: Name or service not known
0: Unknown host

Version-Release number of selected component (if applicable):
8

How reproducible:
example, on a mail server, 'telnet 0 25' should connect to localhost:25

Steps to Reproduce:
1. telnet 0 25
2.
3.
  
Actual results:
telnet: 0: Name or service not known
0: Unknown host

Expected results:
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.

Additional info:
This has only been seen on systems running glibc-2.3 or higher
Comment 1 Ulrich Drepper 2004-08-26 04:48:29 UTC 
Seems to work with current versions.  If there was such a bug (I don't
say there wasn't) it has been fixed meanwhile.