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) ? Thanks! On Sat, Mar 29, 2008 at 12:56 PM, Renaud Deraison (lists) < [EMAIL PROTECTED]> wrote: > > > Hi Shavian, > > On Mar 29, 2008, at 8:21 PM, Shavian Shakes wrote: > > > Hi List, > > > > I am running nessus v3.2.0 on Windows XP. > > > > For my private testing, I would like to modify some nasl scripts > > (and later write my own). > > > > To start with, I modified a script (sql_injection.nasl). The only > > change i did was change a string in the report message. For this I > > just edited the file and changed it. > > > > The problem is that when I run the nessus client and the > > sql_injection succeeds, I still get the old message and not the new > > one which I put in. > > > Yes, on Windows you need to run build.exe which will re-process the > nasl files and include your changes. > > > > -- Renaud > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus >
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
