> One option might be to use a Perl script I wrote a couple of years ago, > describe-nessus-plugin. It parses the script description in NASL plugins > and outputs selected fields such as script id, CVE id, risk factor, etc. > I've only used it on *nix systems, but I don't see why it wouldn't work > on Windows too as long as you have the requisite modules (in particular, > Text::Balanced and Text::Wrap). It's available at: > > http://www.tifaware.com/perl/describe-nessus-plugin/ > > You could then use describe-nessus-plugin in another script that > iterates over the NASL plugins in a given directory and produces the > table with the information you're interested in.
Thanks. I installed Perl on my scanning machine and your script runs without needing any modifications, which is good since I don't really know much Perl. (Under Windows, wildcards don't get expanded by the shell, so as you mention in the last paragraph, I had to run the script ~15,000 times with the FOR command. It took 21 minutes. I suspect that doing the expansion in the Perl script would not greatly reduce this time.) FYI, I got messages "does not have a description part!" for 12 scripts that just say "exit(0)" and one "Unmatched opening bracket(s)" for a code fragment in the comments section. _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
