Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: nasl command line output |
|---|---|
| Date: | Fri, 27 Jul 2007 14:40:15 +0200 |
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 Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Update File Enumeration, jfvanmeter |
|---|---|
| Next by Date: | Re: nasl command line output, Renaud Deraison |
| Previous by Thread: | Re: nasl command line output, Ron Gula |
| Next by Thread: | Re: nasl command line output, Renaud Deraison |
| Indexes: | [Date] [Thread] [Top] [All Lists] |