On Sat, 19 Jul 2003, Michel Arboi wrote: | Fyodor <[EMAIL PROTECTED]> writes: | > But I find it hard to believe that maintaining an entire copy of the | > Nmap source tree within Nessus will be easier. | | Well, there are 3 options: | A) Maintain a private copy of Nmap | B) Implement "parallel" plugins in Nessus | C) Modify Nmap to use less memory, or at least use shared memory.
If you're starting a fund, add my $.02 to the nmapd idea. or at least some IPC that allows us to add IPs after it's launched. Fyodor, would it be possible to insert addresses to scan after starting? (I haven't looked at the code in years, and I would probably get cornfused anyway, since I only speak enough C to coredump "Hello, world") Alternatively, since it's apparent that a single instance of nmap will scan all addresses in parallel, can you add an option to limit how many hosts to scan at a time? (or at least how many hosts to start with, then backfill the queue?) My thought is that if I've told Nessus to scan 8 hosts at a time, I'd like nmap to finish scanning 8 hosts right away so Nessus can start banging on the ports. The rest of the nmap scans can continue, and Nessus can buffer nmap's output until it's ready for another host. .nhoJ
