Quick question...
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.
What exactly is the behaviour expected here? My puzzlement
stems from the fact that find_service.nes already identifies
web servers, which would suggest that putting in port 80
might be redundant. The fact that the same plugins work for
SSL servers suggests that there is an "OR" operation going on,
and that the real trick is for Services/www to be set via
find_service.
On the other hand, find_service isn't necessarily always run,
(no port scan done?) which means that having port 80 specified
can allow the plugin to still run...
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?
Thanks, Thomas
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
