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]

Re: nasl command line output

Subject: Re: nasl command line output
Date: Fri, 27 Jul 2007 06:36:56 -0400
The plugins you are running may be writing to the KB and not directly
reporting. Also, the plugins you are running might not be working the
way you expect them to. Have you tried tracing them with the -T option
to make sure they are executing correctly?

Ron Gula

Richard van den Berg wrote:
I use the nasl command line tool all the time to manually run nasl 
scripts. I was very surprised to see the blog entry at 
http://blog.tenablesecurity.com/2007/06/using-the-nasl-.html display 
actual output from a nasl script. All I get when I run nasl on the 
command line is "Succes!" or nothing (meaning failure).

Is there a way for the nasl command line tool to actually display the 
output from the security_hole() and security_warning() nasl functions?
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>