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 in Nessus Report |
|---|---|
| Date: | Wed, 19 Mar 2008 23:01:47 -0400 |
Yanyan Wang wrote:
It might be interesting, though, to have Nessus call it indirectly, via a wrapper such as the following:
You could also edit Nikto's config.txt and set CLIOPTS to something like this: CLIOPTS=-o /tmp/nikto_output.txt Any time Nikto runs, no matter what starts it, the output will go to that file. This may help diagnose what/how Nessus is calling the script. _______________________________________________ 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 in Nessus Report, Yanyan Wang |
|---|---|
| Next by Date: | Re: Nikto in Nessus Report, George A. Theall |
| Previous by Thread: | Re: Nikto in Nessus Report, Yanyan Wang |
| Next by Thread: | Re: Nikto in Nessus Report, George A. Theall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |