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: Nessus Client/Command Line differences

Subject: Re: Nessus Client/Command Line differences
Date: Wed, 11 Jul 2007 15:30:01 -0400
On 07/11/07 13:24, Will Cladek wrote:

I was doing some testing with Nessus and found that one of the
plugins only seems to run when using the Linux Nessus Client and not
the command line.  
...
Any idea why this would be happening, or has anything experienced
this with other plugins?

Is the behaviour repeatable if you rescan the host?

Is there anything in the nessusd.messages log that might suggest what 
the problem is?

It might also be interesting to examine the KB file for the host after 
you've run each scan. This might require enabling KB saving in your 
configuration (eg, with "save_knowledge_base = yes" in the config).

George
-- 
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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