Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: Re: [BUG] NSE/Nsock filehandle exhaustion

Re: [BUG] NSE/Nsock filehandle exhaustion

From: Fyodor <fyodor_at_insecure.org>
Date: Thu, 30 Aug 2007 14:34:42 -0700

On Thu, Aug 30, 2007 at 08:45:34PM +0200, majek04 wrote:
> On 8/28/07, Brandon Enright <bmenrigh_at_ucsd.edu> wrote:
>
> I implemented it exactly as you proposed. nsock_connect blocks when the
> number of opened connections exceeds some threshold.
>
> For this moment this threshold is hardcoded in
> #define NSOCK_DESCRIPTORS_THRESHOLD 768

Hi Marek. This patch looks great, thanks! I've changed it to use
o.max_parallelism instead, which is designed for this purpose. Also,
Brandon made a great point about a script which might open several
sockets at once (for example an identd-checking script). So I made it
always allow at least 10 concurrent sockets. I checked the result
into SVN. It seems to work from my testing, but I only tested a
couple machines -- not enough to actually reach the limit.

Cheers,
-F

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Aug 30 2007

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos