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: Nikto Result Problem When Nikto is Integrated in Nessus

Subject: Re: Nikto Result Problem When Nikto is Integrated in Nessus
Date: Wed, 01 Aug 2007 20:53:55 -0400
On 08/01/07 04:58, kemal ayten wrote:

I send yo to nessj network logs which show all configuration details.

Actually, I was looking for a configuration file, not an NTP protocol trace.

I use same input in my own C# cilent, I am also obtain nikto result 
sometimes sometimes not.

You're saying the same client / target(s) / configuration sometimes give 
you results and sometimes they don't, right? If so, focus on one 
specific client, preferably either the NessusClient / nessus commandline 
clients. Continuing to bring multiple clients into the picture only 
makes things more confusing.

Are any error messages being logged to nessusd.dump when you run these 
scans? Are web servers listening on the target(s) when you run these 
scans but don't get any results?

I'm also curious to hear an answer to Michel's question, about whether 
no404 was set.

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>