Bug 111626 - telnet 0 fails with latest glibc
Summary: telnet 0 fails with latest glibc
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-06 20:13 UTC by Abel Lopez
Modified: 2016-11-24 14:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-26 04:48:29 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.