Re: Nmap (NASL Wrapper) not generating correct nmap command-line

On Jan 6, 2006, at 11:06, Martin MaÄok wrote:

> On Fri, Jan 06, 2006 at 10:22:04AM +0100, Michel Arboi wrote:
>
> > Current Nmap versions eat too much memory for each process.
>
> This is not true anymore. Since Nmap version 3.95 (to be more precise,
> 3.94ALPHA2) it doesn't allocate an object for each tested port and the
> memory consumption is much lower than before.
>
> http://www.insecure.org/nmap/changelog.html
>
> (Or is it still not enough?)

The fact is that even if Nmap was using one byte of memory, it would  
still not be a very good idea to use it when doing a network scan  
because its code is loaded multiple times in memory (once per  
process). So memory is wasted _anyways_ (the amount of memory changes  
from one OS to another).

Using Nmap when doing a Nessus scan of one host or two is doable, but  
if you intend to scan up several hosts in parallel you probably don't  
want to use it -- either run it prior to the scan and import the  
results in nessusd, or use nessus_tcp_scanner which adapts its  
timeout for each tested host.



                                        -- Renaud

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus