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 [email protected] http://mail.nessus.org/mailman/listinfo/nessus
