On Mon May 30 2005 at 13:58, Herman Young wrote: > Recent changes to nmap affects the time it takes to port scan a firewalled > host. This will in turn affect Nessus scans when nmap.nasl is used. What about removing most of the code, and have nmap.nasl just import a file? I sometimes think this is the best option. > Reference: http://seclists.org/lists/nmap-dev/2004/Oct-Dec/0143.html (Nmap > Development: nmap-3.7x MUCH slower than nmap-3.55 against firewalled hosts) nessus_tcp_scanner does not suffer from this, AFAIK. > The workaround for this issue is to pass additional parameters to nmap > namely (--max_scan_delay 0). According to the manual page, the timing (-T) options changed this parameter. Did you play with them? > script_add_preference(name: "Maximum wait between probes (ms)", value: "", > type: "entry"); There are already too many preferences. I'd rather not add one. Maybe this could be automatically added when we are not in "safe checks"... _______________________________________________ Plugins-writers mailing list Plugins-writers@private http://mail.nessus.org/mailman/listinfo/plugins-writers
This archive was generated by hypermail 2.1.3 : Tue Jun 14 2005 - 01:47:05 PDT