Nmap Development mailing list archives

Re: Suggestion syntax (was:Script suggestions, take #3)


From: David Fifield <david () bamsoftware com>
Date: Wed, 14 Mar 2012 21:15:47 -0700

On Thu, Feb 09, 2012 at 10:46:01AM +0100, Martin Holst Swende wrote:
Hi list,
Changing the topic, let's ignore the under-the-hood stuff for now.

I'd like to get feedback on the proposed syntax for script-suggest.
Right now,
we have two different versions.
1. --script-suggest <rules> and -sCS working in parallell with and
identical to --script <rules> and -sC
2. --script <rules>,$<rules>  , where $ (or whatever character we
choose) is a flag meaning "use this rule for suggestions", similar to
the force-flag.

Currently, [1] is implemented (based on discussions in
http://seclists.org/nmap-dev/2011/q4/389) and involved quite a lot of
changes here and there. [2] is not implemented, but would mean less
overall changes in the nmap framework. My personal preference is [1],
Patrick leans towards [2]. David, Fyodor, Patrik, Duarte?

Martin, I'm sorry this has gone so long without a decision. I think the
feeling is that this isn't useful enough to justify a new option or new
--script syntax.

But I'm still open to being convinced. Would you create a branch for
this patch in your nmap-exp directory? Then it will be a bit easier to
test and run. Also, because I'm a bit worried about the manitainability
of the script args parser, having a working branch will be a test at how
well it can cope with other NSE changes.

I don't like the $ prefix idea. --script-suggest is better, but I still
don't like it much. -sCS conflicts with established use that -sCS is the
same as -sC -sS.

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


Current thread: