Re: Proposal for ncat improvement

Dear nnposter,
this was a perfect answer -- of course it helped to solve my little issue of missing the http-response due to connection closing by ncat. With the mentioned option
--no-shutdown it behaves exactly as wanted. Thanks a lot.

Btw., as I am using nmap on Windows/DOS, I was not aware of the above option for ncat. The Usage/Help of ncat under DOS does no mention the --no-shutdown option. Looking up the man page for ncat on Linux I found it well documented in the usage/help output.

Cheers,
Uli

________________________________
From: dev <[email protected]> on behalf of nnposter <[email protected]>
Sent: Tuesday, December 11, 2018 21:41
To: [email protected]
Subject: Re: Proposal for ncat improvement


On 12/11/18 5:01 PM, Ulrich Heuser wrote:
> Dear all,
> I found a relevant diff between the original netcat tool and ncat out of
> nmap:
>
> On sending out a http-request by netcat the connection is kept alive for
> a long period, and this supports receiving a http-response from the
> addressed counterpart.
>
> With ncat the connection is closed after 1 sec., and the comm.
> counterpart is not able to send a http-response to the ncat requestor
> after that amount of time.
>
>
> It would be useful to extend the options of ncat by a keep-alive
> time-val. and to keep the connection open for such given period to allow

While not exactly the same, would option --no-shutdown help in your
situation?

Cheers,
nnposter
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/