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]

Nikto in Nessus Report

Subject: Nikto in Nessus Report
Date: Thu, 13 Mar 2008 16:34:17 -0400
Hi There,

I integrated Nikto into Nessus recently, and Nikto,nasl shows from the client 
side. I scanned one host to test If Nikto is indeed working. Here is what I did 
in order:

1. Disable Nikto from plugins, result shows there are 2 high vul. 0 medium 
vul...
2. Enable Nikto from plugins, the report is identical in 1.
3. Enable Nikto from plugins and plugins preference, result shows 2 high vul. 
and 3 medium risks.
4. Disable Nikto from plugins, the result is identical as in 3.
5. Disable Nikto from plugins and preferences, the result is still the same as 
in 3.

kb_restore is disabled. I did not find 14260 or Nikto in any of the report. Can 
someone please explain a few questions I have?

1. Why step 1 to step 2 didn't differ, but step 2 to 3 did?
2. Why step 3, 4, 5 are identical? 
3. Is Nikto indeed working? If it does, shouldn't I see the ID no. from the 
report? 

My system infor: OpenSuse 10.3, Nessus 3.2.0, Nikto 2.02

Thanks. 

YanYan


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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