Re: How to correctly modify nmap.nasl?
Michel Arboi <[email protected]>
| Newsgroups | gmane.comp.security.nessus.general |
|---|---|
| Organization | nessus.org |
| Message-ID | <20080508192903.44d4eefb@rotissoire> |
On Thu, 8 May 2008 10:49:22 -0400 James Birk <[email protected]> wrote: > I'm not sure what's wrong with using Nmap along with Nessus - incompatible licence - incompatible architecture - huge resource consumption, especially when several Nmap processes are launched in parallel and all allocated dozens of MB of private memory to store the same information. - try to find detailed information where Nessus only needs open ports. The consequence of the last point is that Nmap becomes sluggish in some vicious situations. nessus_tcp_scanner just grabs the open ports and does not care if the remaining ports are closed, filtered, firewalled, or even NATed to the moon with a RTT > 2.4 s. > Against many sorts of targets, Nmap's biggest plus is that if you're > fast on the command line, it's lightning fast as a method of sketching > out a rough picture of some of the issues you can expect to find in a > target OK but that was not the topic. Feeding Nessus with Nmap results may make sense, but running Nmap *from* Nessus just does not. _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus