Ron Gula wrote: > The plugins you are running may be writing to the KB and not directly > reporting.
AFAIK all plugins are writing to the KB, and none of them "report directly". Common practice is to use security_hole(), security_warning() or security_note() to do reporting. However, the blog entry made it look like the nasl command line tool can be used to view the output of a plugin directly. > Have you tried tracing them with the -T option > to make sure they are executing correctly? Yes I did. Tracing with -T shows the plugin works fine. I'm using Nessus 3.0.5 at the moment. Sincerely, Richard van den Berg _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
