Bug 1724602

Summary:	[ncat] no output when sctp, but tcp/udp has
Product:	[Fedora] Fedora	Reporter:	Pavel Zhukov <pzhukov>
Component:	nmap	Assignee:	Martin Osvald 🛹 <mosvald>
Status:	ASSIGNED ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	39	CC:	mhlavink, mosvald, pzhukov
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Pavel Zhukov 2019-06-27 11:39:58 UTC

This bug was initially created as a copy of Bug #1724416

I am copying this bug because: 



Description of problem:
In this format:  
echo ncat --sctp -l 127.0.0.1 | bash
ncat no output for sctp, but tcp/udp has

Version-Release number of selected component (if applicable):
nmap-ncat-7.70-4.el8.x86_64
nmap-ncat-6.40-19.el7.x86_64
Both exists on RHEL7 and RHEL8

How reproducible:
always

Steps to Reproduce:
1.
# echo ncat -l 127.0.0.1 2000 |bash
abc
# echo ncat -u -l 127.0.0.1 2000 |bash
abc
# echo ncat --sctp -l 127.0.0.1 2000 |bash
#
Get nothing here!

2.
At another terminal
# ncat  127.0.0.1 2000 <<<'abc'
# ncat -u 127.0.0.1 2000 <<<'abc'
# ncat --sctp 127.0.0.1 2000 <<<'abc'

3.

Actual results:
# echo ncat --sctp -l 127.0.0.1 2000 |bash
This command returned but has no ouput.

Expected results:
ncat --sctp work as expected.

Additional info:
This issue affect our test script. Please fix it.

Comment 1 Ben Cotton 2019-08-13 16:56:05 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 19:08:32 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Ben Cotton 2020-08-11 13:06:27 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Ben Cotton 2021-02-09 15:10:07 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 5 Ben Cotton 2022-05-12 16:56:57 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-08-09 13:41:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 7 Fedora Release Engineering 2023-08-16 07:04:22 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.