New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv4 fallback support is missing from ncat #157
Comments
+1 for getting this deficit fixed |
see this email for updated patch with addressed comments http://seclists.org/nmap-dev/2015/q2/92 |
I disagree that this is an "enhancement". This is a serious bug and lack of feature parity that causes serious issues when trying to use ncat as a replacement for nc. |
I second @quanah. |
Hello folks, |
Fixed in 4629f6d with patch via http://seclists.org/nmap-dev/2015/q2/92 |
As discussed in this thread from 2 years ago:
http://seclists.org/nmap-dev/2013/q4/269
ncat does not have IPv4 fallback. This is a serious deficiency and lack of feature parity with the other nc implementation. It makes ncat essentially unusable on systems that have both ipv4 and ipv6 localhost defined, but only have services listening on the ipv4 localhost.
With only ipv4 localhost defined:
[root@zqa-226 ncat]# echo STATUS | ./ncat -w 15 localhost 7171
SUCCESS ACTIVE[root@zqa-226 ncat]#
After defining ::1 to localhost:
[root@zqa-226 ncat]# echo STATUS | ./ncat -w 15 localhost 7171
Ncat: Connection refused
The text was updated successfully, but these errors were encountered: