Dear all: I'm very interested in composing new OpenVAS plugins using nasl language, but I cannot find a decent way to test them. So far my approach is:
1. Copy the new plugins into OpenVAS plugin directory(/usr/local/var/lib/openvas/plugins). 2. Run "openvassd" and "openvasmd --update" to let OpenVAS actually sees the newly added ones. 3. Create a scan template including those newly added plugins. Here I'm using gsd on my own machine to do this remotely, and create a task that using this template and pointing to a pre-configured target machine. 4. Run the task and wait for the report. I admit that I'm pretty new in writing OpenVAS plugins, so I'm still on my way of finding a feasible way to do it. However, the method that I adopt is extremely time-consuming. Thus I need the answers to these questions: 1. Do I need to add all the dependencies for the new plugin into the template to test them? Or OpenVAS is smart enough to go back and fetch those automatically? (I assume the answer is yes, because if I don't add those dependencies, the report might give out "ssh port is not open, might not able to perform local checks" in the report.) 2. Is there any other way that we can only test for certain plugins? I could use "openvas-nasl" command to test the syntactic correctness, but I need a quick way to determine whether they are working or not. It's also welcomed to share any experience for writing plugins and testing methods. I really appreciate it. cheers, Shang
_______________________________________________ Openvas-plugins mailing list [email protected] http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-plugins
