On Wed, Sep 14, 2005 at 04:33:29PM +0200, I am WE4SEL wrote: > So if I got you right to make sure that the nmap wrapper finds a host > the way the standalone nmap does I have to disable dependencies of > plug-ins.
That's one way. Other is to make sure you pick an appropriate port range for ping_host.nasl. > Ok, I can do that but does this have other side effects? Yes, certainly. If you don't explicitly enable plugins that are listed as dependencies for other scripts, they won't be run, and that will likely lead to problems with those other plugins. For example, several Mozilla / Firefox / Thunderbird-related scripts rely on mozilla_firefox_code_exec.nasl to actually determine whether the software's installed and, if so, its version number. If you don't explicitly enable that plugin, the Mozilla / Firefox / Thunderbird scripts won't report any problems. > Actually, I would prefer this over the extended TCP ping option. Even if > the scan takes longer. What do you propose? Feed nessus output from nmap. > Another question is this fragmented option of nmap. Martin Mačok has answered that. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
