Bug 695571

Summary: Netcat generates illegible error message
Product: [Fedora] Fedora Reporter: Rob Gilton <rob>
Component: ncAssignee: Petr Šabata <psabata>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: mark.dickinson, psabata, rvokal
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: 2011-04-12 08:28:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Rob Gilton 2011-04-12 03:10:26 UTC 
Description of problem:
Netcat spews an illegible error message.

Version-Release number of selected component (if applicable):
nc-1.100-1.fc14.i686

How reproducible:
Always.

Steps to Reproduce:
1. Run `nc localhost 22`
  
Actual results:
Netcat aborts and displays: "nc: port number ���"���,���: 22"

Expected results:
Should connect me through to the local ssh machine.

Additional info:
Not specific to localhost, nor the port number.
Comment 1 mark.dickinson 2011-04-12 06:50:10 UTC 
[mark@eagle ~]$ rpm -qf /usr/bin/nc
nc-1.100-1.fc14.i686

I have the same problem on FC14 after doing a yum update last weekend. 
The nc does not seem to connect to the specified port number, in that an nc listening doesn't end when using nc to connect to the listening port, indicating no session was started to be terminated.
nc still listens ok.

telnet will connect to a listening nc which ends when the session does.
[mark@eagle ~]$ rpm -qf /usr/bin/nc
nc-1.100-1.fc14.i686

[mark@eagle ~]$ nc -l localhost 1099
[mark@eagle ~]$ echo "xxx" | nc localhost 1099
nc: port number æÇ¿éÇ¿óÇ¿: 1099

[mark@eagle ~]$ telnet localhost 1099
Trying ::1...
Connected to localhost.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

"yum downgrade nc" took me back to nc.i686 0:1.84-23.fc14 which works as expected.
Comment 2 Petr Šabata 2011-04-12 08:28:35 UTC 

*** This bug has been marked as a duplicate of bug 694407 ***