Re: Forcing scripts to run?

[Fyodor <fyodor () insecure org>]

On Mon, Jul 12, 2010 at 11:26:18AM -0500, Ron wrote:
> I was helping somebody resolve an issue this morning, and realized
> there's a feature missing from NSE that maybe ought to be there:
> forcing a script to run against a host and/or port in spite of its
> hostrule/portrule.

Yes, I can see value in that.

> Any ideas how it could work? I imagine this as similar to
> --version-all, except it would be running every script against every
> host/port.

One option would be to do this in NSE.  The vast majority of the
scripts use the shortport.* functions, so a script arg could be added
to functions like shortport.version_port_or_service even if the port
number or service name don't match.  An advantage of this approach
(versus an Nmap argument which skips the rule check) is that other
aspects of the rules can still apply.  For example, you would
generally still want the OpenSSL check.  Trying to run a TCP script
against a UDP port or vice versa could be problematic as well.  So the
protocol check might be worth keeping.

Cheers,
-F
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/