On Wed, Sep 11, 2002 at 02:03:44PM -0400, Thomas Reinke wrote:
> The API script_require_ports is puzzling me just a bit that
> I wanted to confirm something: the typical usage is to pass
> in two parameters, eg. "Services/www" and 80
> if the test is a web server test.
The point is to let the plugin run if find_services is not enabled
during the scan (which would be *bad*, but if that happens, not testing
port 80 just because Services/www is not set would be stupid too).
[...]
> Im guessing that:
> a) Either port or servicename defined results in a script being
> invoked on the specified port associated with the service,
> or the port itself.
>
> b) That having port 80 is for convenience more than anything else
> when port scans may not have been run, allowing all scripts to
> be at least invoked against a typical web server install on port
> 80.
>
> c) Multiple services matching the Services/www key result in
> multiple scripts being invoked, one for each found port/service
> possibility.
>
> Did I get that right?
Roughly yes, except that for (c), the script will be invoked once but
will fork (codewise in nessusd it's only one script, even if there is
two hundred web servers on the remote port).
-- Renaud
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
