Re: Nikto in Nessus Report

On Mar 19, 2008, at 10:21 PM, Yanyan Wang wrote:

> I did as you told, nothing happened. I ran the wrapper alone. It  
> worked fine and the log output the scan results.

Did Nessus find a web server on the target(s)? Does the web server  
fail to generate 404 response codes by any chance? Could you send me a  
KB from one of the targets when you've tried to run the Nikto plugin?

> I edited nikto.nasl,

It's a trusted script so unless you set 'nasl_no_signature_check =  
yes' in your nessusd.conf, editing the plugin will prevent it from  
running.

> and changed all default add preferences value from "no" to "yes",  
> but the client didn't update the change (two different clients).  
> I've tried to restart the server and the client, it still didn't.

If you're using NessusClient, you will need to create a new policy to  
see the changes. [And restart the server, of course.]

> One more thing, nessus serve often doesn't stop cleanly. Sometimes  
> it leaves a process hanging. I usually have to kill nessus processes  
> to have it run properly again. Thank you.

Are you sure it's not the case that the processes are taken a while to  
exit?

George
-- 
theall@tenablesecurity.com



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