On Apr 10, 2008, at 6:24 AM, Mude Mude wrote:
1. is nessus capable of calling/executing perl scripts and make
nessus do all the reports?
I'm not exactly clear what you're asking. It sounds like you're
interested in filtering reports in some fashion. If so, no, it's not
possible, at least with NessusClient. But there's no reason you can't
have a script that calls the Nessus client and output the results to a
temporary file and then post-process them.
2. is this the right way to add my own nasl script? coz it wont show
up in the client sometimes.
- /etc/init.d/nessusd stop
- nessus-update-plugins -v
- /etc/init.d/nessusd start
-reconnect client
Not exactly. nessus-update-plugins will try to fetch the latest
tarball from Tenable. You probably don't need to use it *when you're
just adding your own plugin.
You do need to make sure that your plugin compiles cleanly, that it
uses a unique script_id (we recommend using an id in the range 60000 -
62000), and that the script_name is unique as well. Then, copy the
plugin to the plugins directory and send the main nessusd process a
HUP signal. Lastly, reconnect with your client.
If you don't see the plugin in the client, create a new policy -- it
should appear in that.
3. is there a one liner command to add just 1 nasl plugin?
I don't understand the question.
4. when i revise my nasl script, is this command enough for the
changes to take effect?
- /etc/init.d/nessusd restart
- reconnect client
I tend to use "nessusd -t", which causes Nessus to check the timestamp
of each plugin when deciding whether to rebuild the plugins database.
As long as your talking about changes to an existing plugin and those
changes aren't in the plugin's description block, you don't need to
reconnect the client.
George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
