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. |

| Subject: | Re: Nikto Result Problem When Nikto is Integrated in Nessus |
|---|---|
| Date: | Tue, 31 Jul 2007 10:18:00 +0300 |
I use the words unstabilities since I can obtain nikto results from other clients such as NessWX and NessusClients(Boss) but this is not stable.Inother words I sometimes obtain results sometimes not although conditions are same. This is also true for NessJ clients when I choose nikto and also other plugins. I choose nikto plugin and also related two preferences Enable Nikto test and Force Full(generic) scan. When I look at the nessus.messages logs , I see that in every case ,whether I obtain result or not, nikto.nasl plugin is launched.But the messages which show the time of jobs different.So I try to use different timeout values but I could not solve the my problem. Thank you for your attention. Kemal Ayten On 7/31/07, George A. Theall <theall@tenablesecurity.com> wrote:
On 07/30/07 11:07, kemal ayten wrote:My problem is that sometimes I obtain nikto result in nessus report sometimes I can't.There is no stable nikto result altough similar scannin configuration....I try to find reasons of nikto results' unstabilities.What exactly do you mean by "unstabilities"? From your message, it seems like you get results only when you use Nessj; otherwise, the plugin runs but exits immediately / almost immediately. This suggests the problem is not one of the plugin's stability but rather that you're having trouble properly configuring the clients: subtle differences in the configurations could very easily explain the different / lack of results you're seeing. For example, when you don't get any results, have you specifically enabled the Nikto plugin? You not only need to select the plugin but there's also a preference ("Enable Nikto") that must checked or the plugin exits immediately. George -- theall@tenablesecurity.com _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Nikto Result Problem When Nikto is Integrated in Nessus, George A. Theall |
|---|---|
| Next by Date: | Re: Nikto Result Problem When Nikto is Integrated in Nessus, Michel Arboi |
| Previous by Thread: | Re: Nikto Result Problem When Nikto is Integrated in Nessus, George A. Theall |
| Next by Thread: | Re: Nikto Result Problem When Nikto is Integrated in Nessus, George A. Theall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |