Thought crossed my mind...is it worth it to modify the
scripts to have the first line read "#!/usr/local/bin/nasl" ?
The obvious advantage: running a script against your favourite
target is now a case of saying
myscript.nasl -t IP
Rambling on a bit more, it occurs to me that given the problems
with running the command line programs on an ongoing basis,
one could expand the above to do a number of 'wonderful' things:
1) Know where to pick up the scripts and automatigcally run
dependendent scripts (e.g. -d)
2) Support multiple IP addresses, etc.
Yes, it's to a certain extent reinventing the wheel a bit. But
it provides a real quick, easy, one-shot way of running one
test against a network, pick up the test's dependencies, and
possibly even be able to do some SIMPLE things like specify port
ranges to populate into the kb so the test works properly, etc.
Not that this can't be done thorugh an alternate mechanism...but
I've never found the alternate mechanisms to be incredibly user
friendly. Doing the above leverages the paradigm shell script
programmers already know and love: write the script, run the
_script_.
And the changes to the existing test scripts doesn't even affect
the existing daemon, since addition of a banner line would
already be treated as a comment.
Just some thoughts,
Cheers, Thomas
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
