You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How should ncat behave if the users want it to send something back?
A warning once if recvonly == false and then ignoring all writes would be fine, or?
I am wrong, the issue still exists. The changes I mentioned should make it safe to print debug messages regarding such a connection, but it does not address the issue of calling connect() on such a socket.
Definitely affects SOCK_DGRAM (
--udp
), but may also have impact on SOCK_STREAM (TCP-style, the default). See http://seclists.org/nmap-dev/2014/q4/343 and #23The text was updated successfully, but these errors were encountered: