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: max_sd() upper limit hardcoded 250?

max_sd() upper limit hardcoded 250?

From: William McVey <wam_at_cisco.com>
Date: 16 Jul 2002 17:43:55 -0500

I grew tired of seeing the:
        WARNING: Your specified max_parallel_sockets of XXX,
        but your system says it might only give us 250. Trying anyway
error/warning message, so I looked into some. This message comes
because the -M option is being compared to the result of max_sd() (from
tcpip.c). The max_sd function though has a hardcoded limit of 250 with
a comment saying:
        /* I do not feel comfortable going over 255 for now .. */

The max_sd() function is only called in three places. Once for the -M
warning and twice to set a default max_width for connect scans. In the
case of the warning, the arbitrary limit of 250 turns the warning into
an incorrect statement (since the system is happy providing more
sockets). For setting the default max_width, it seems probably better
to use something like MAX_SOCKETS_ALLOWED, or constructing a new #define
for this value (and ideally taking it out of the max_sd() function).

  -- William

---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to
nmap-dev-help_at_insecure.org . List run by ezmlm-idx (www.ezmlm.org).
Received on Jul 16 2002

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