Jared
To help determine if Nikto is even running against the target, you can edit
Nikto's config.txt and enable the CLIOPTS setting and have it dump all output to a file. When it runs, anything being printed by Nikto will also be saved to this file. For example:
CLIOPTS=-o /tmp/output.txt
This may help debug where exactly the problem is (calling nikto, nikto running, output going back to nessus, etc.).
Hmm... this is interesting. I added the CLIOPTS line to my nikto.cfg file as suggested and ran a nikto scan. Sure enough, all output was copied to /tmp/output.txt. I then deleted the file and ran a Nessus scan, with nikto enabled, against the same host. According nessusd.messages, nikto.nasl was launched, but it exited after 0.009 seconds, and NO OUTPUT was copied to /tmp/output.txt.
So, it looks like the plugin is running, but for some reason it's not actually firing off Nikto. Getting closer... :-)
Is there any extra debugging I can do in Nessus itself? Something to give me a better indication of what's going wrong?
Thanks, -- Jared
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
