Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to write a nessus plugin. So I took an existing plugin (10056), and only added the line display("hello world"); in the appropriate section and altered the script_id to a non-existing one. I chose that plugin because that is one that gets found on a test machine. This modified plugin is saved in the typical folder /opt/nessus/lib/nessus/plugins with all the other plugins as pesa.nasl.

A test-run with nasl -t pesa.nasl prints the expected "hello world".

But when I run nessus again, after re-starting the daemon, the plugin doesn't get detected. Not when I look into the findings list, and also it's nowhere in the policies part that shows the plugins.

Any ideas what I need to do additionally, that nessus reads my self-written plugins?

share|improve this question

closed as off topic by Rory Alsop Aug 4 '12 at 19:55

Questions on Information Security Stack Exchange are expected to relate to Information security within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 0 down vote accepted

It seems that nessus-update-plugins doesn't only fetch the newest updates from the nessus servers, but also tells the daemon about the new files that are placed in the plugin folder. So /opt/nessus/sbin/nessus-update-plugins does the job.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.