Regarding the Sept post on blog.tenable.com regarding nessus calling and
executing "nikto" it states:
"Finally, nikto.nasl is disabled by default in the scan policy. To change
this under NessusClient3 for example, edit the policy and click on the
'Advanced' tab. In the drop down menu, select "Nikto (NASL wrapper)" and
change "Enable Nikto" from 'no' to 'yes'."
After following the configuration on a redhat es4 server i am able to
complete the following:
call nikto.pl from any directory
display the nikto.nasl (14260) under the plugins tab, as well see it in the
plugin lib
But referring to the quote above i don't have this option available under
any of my policies. This is true for any connecting clients. I have Nessus
Client for windows v3.2.1 (build 2G299_Q) as well a X-window redirecting my
server's NessusClient v3.2.1 (build 2G295_Q). Neither have this option
available. I'm running the latest nessus server.
Am i missing something?
ashby
executing "nikto" it states:
"Finally, nikto.nasl is disabled by default in the scan policy. To change
this under NessusClient3 for example, edit the policy and click on the
'Advanced' tab. In the drop down menu, select "Nikto (NASL wrapper)" and
change "Enable Nikto" from 'no' to 'yes'."
After following the configuration on a redhat es4 server i am able to
complete the following:
call nikto.pl from any directory
display the nikto.nasl (14260) under the plugins tab, as well see it in the
plugin lib
But referring to the quote above i don't have this option available under
any of my policies. This is true for any connecting clients. I have Nessus
Client for windows v3.2.1 (build 2G299_Q) as well a X-window redirecting my
server's NessusClient v3.2.1 (build 2G295_Q). Neither have this option
available. I'm running the latest nessus server.
Am i missing something?
ashby