Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Ncat accepting connections without --keep-open
From: Shinnok <admin () shinnok com>
Date: Tue, 21 Jun 2011 01:23:15 +0300

On 06/19/2011 01:14 AM, Shinnok wrote:

Yes, it sounds like Ncat should close its socket after accepting its
first connection. Would you write a test for how it's supposed to work?

David Fifield
Done in r24197.

Should closing the socket take effect in case of --max-conns also? Or
allow just the number of connections specified and then close as soon as
that number is achieved?

Eg. from the man page for context:

--
Bind a shell to TCP port 8081, limit access to hosts on a local
network and limit the maximum number of simultaneous connections
to three

ncat --exec “/bin/bash” --max-conns 3 --allow 192.168.0.0/24 -l
8081
---

The above examples doesn't specify --keep-open.


I'm afraid I'm going to have to push this one up a little bit, since I
need an answer in order to know how to proceed.

Should --max-conns take effect only in server listening modes(-k,
--chat, --broker) or single listening too?

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault