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.




Network Security Nessus-Users
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: nasl command line output

from [Renaud Deraison] Network Security [Permanent Link]
Subject: Re: nasl command line output
Date: Fri, 27 Jul 2007 14:45:46 +0200 

On Jul 27, 2007, at 2:40 PM, Richard van den Berg wrote:


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.


If the plugin calls security_note() or security_note(port) then you  
only get 'Success'. If the plugin calls security_note(port:port,  
data:whatever) then you'll get the full output.


Sorry for the confusion,

                                -- Renaud
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: nasl command line output, Richard van den Berg
Next by Date:  Update File Enumeration, jfvanmeter
Previous by Thread:  Re: nasl command line output, Richard van den Berg
Next by Thread:  Nessus 3.06 versus WSUS conflict, ablesambaker
Indexes:  [Date] [Thread] [Top] [All Lists]