Bug 1591959

Summary:	Please include https://github.com/nmap/nmap/commit/ec38cb0096648e916660958ac48c121e303debf1
Product:	Red Hat Enterprise Linux 7	Reporter:	Phil Dibowitz <phil>
Component:	nmap	Assignee:	Pavel Zhukov <pzhukov>
Status:	CLOSED ERRATA	QA Contact:	Robin Hack <rhack>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	7.5	CC:	psklenar, pzhukov, rhack, thozza
Target Milestone:	rc	Keywords:	EasyFix, Patch, Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	nmap-6.40-19.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2120294 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:41:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2120294

Description Phil Dibowitz 2018-06-15 20:52:27 UTC

Description of problem:

As of RHEL 7.5, ipv6 http proxying in nmap-ncat is broken. Please pull https://github.com/nmap/nmap/commit/ec38cb0096648e916660958ac48c121e303debf1 which is a 1-character fix.

Version-Release number of selected component (if applicable): 6.40-13.el7


How reproducible:

try to proxy to a ipv6 literal and watch 400/500 errors (depending on your proxy server), 100%


Additional info:

As I said, already fixed upstream, please pull that patch.

Comment 2 Phil Dibowitz 2018-09-23 14:19:31 UTC

Just wanted to follow-up - any chance of getting this into RHEL updates?

Comment 3 Pavel Zhukov 2018-09-24 06:15:58 UTC

Hello Phil,
Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:
    https://www.redhat.com/support/process/production/#howto

Comment 4 Phil Dibowitz 2018-09-25 09:37:19 UTC

@pzhukov - I'm not looking for support. I'm the one who found the bug, fixed the bug, got the fixed merged upstream, and then filed this to _help_ Redhat fix a regression caused by the rebase RH did on a later version without actually changing the version number.

I'm following up to ask so I know if I need to keep patching internally or if 7.6 will have the fix merged, so I can plan accordingly... and also because I figure your other customers who didn't necessarily do that work would like the fix, and it seemed like a good-community-member thing to do.

Comment 5 Pavel Zhukov 2018-09-25 12:40:52 UTC

Phil,

I'm aware of the bug and upstream change as I participated in GH's discussion. For now I can say we don't plan to include it into 7.6 RHEL release (you can check it in public Beta release). I don't have public information about next release yet.

Comment 16 errata-xmlrpc 2019-08-06 12:41:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2072