Re: Script force

[Martin Holst Swende <martin () swende se>]

> > There is no established terminology here and I was winging it in my
> > post. [There is no real benefit for getting pedantic about command
> > line syntax in user documentation.] To be clear, the proposed change
> > would result in this sort of syntax:
> >
> > --script <outer-expression>
> >
> > <outer-expression> := [prefix] specification { <comma> [prefix] specification }
> > specification := filepath | directory | expression
> > expression := filename-pattern | category | expression binop
> > expression | unop expression
> > binop := and or
> > unop := not
> >
> > filename-pattern only matches files in the script database. Note the
> > pattern can actually be a literal filename.

Here's a new implementation of --force, based on mine and Djalals
earlier versions, but
a bit less complex. Ostensibly, it now works as specified above.

Example syntax:
nmap localhost -p80 --script
"+/home/martin/workspace/nmap-force/scripts/http-title.nse,+http-trace" -d2
nmap localhost -p80 --script "+safe and http-*" -d2

Regards,
Martin

Attachment: nse_main_forcediff
Description:

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