On Sun, Mar 30, 2008 at 12:31 AM, Renaud Deraison (lists) < [EMAIL PROTECTED]> wrote:
> > On Mar 29, 2008, at 10:48 PM, Shavian Shakes wrote: > > > Thanks! That worked! I would never have guessed it was build.exe > > > > I do see the modifications in the nasl file take effect now. > > > > But if I write my own nasl file and then run build.exe, it does not > > show up in the nessus client, I do see that build.exe exits with > > one more plugin installed than the last time (it prints the number > > of plugins installed on the console after finishing its run), so it > > did compile my new plugin I guess. Yet, it does not show up in the > > Nessus client GUI. > > > > I also see my new nasl script entry in the plugins.xml file. Any > > other step that I am missing for this (on Windows) ? > > You need to restart the nessusd service after running build.exe if you > want your plugin to show up, did you do that ? > Yes I restarted it multiple times. It still doesnt show up. The exact sequence of steps I have followed is 1. Create a new nasl file in the plugins/scripts directory 2. test for errors using "nasl -p" -> passes 3. run build.exe (it increments the plugin count, thereby indicating that the new plugin has been compiled) 4. restart nessusd (by toggling the greed/red button on the server gui) and also tried rebooting the machine I have used script id 99999, is there anyplace I have to specify the allowed range of IDs? Thanks!
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
