Well, now I'm confused. I noticed with the new NessusClient that there
was no longer an option to set 'optimize test' and I posted a question
about it. Renaud gave this response
++++++
Hi Scott,
On Jun 10, 2008, at 2:20 PM, Scott Pate wrote:
Unless I am missing something, it seems there are some options missing
from the new NessusClient
-Where is the option to enable/disable "optimize test"?
This option is not exposed any more. Given how we code plugins now,
there is no reason why you would want to use it.
-- Renaud
+++++++
Also, NessusClient has no option for 'optimize test', yet it is still in
the xml file and the default value is set to 'no'. This means I would
have to go into the xml file and change it each time I run a scan.
thx
-----Original Message-----
From: Michel Arboi [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 7:00 AM
To: [email protected]
Cc: Scott Pate
Subject: Re: plugin 33929
On Wednesday 05 November 2008 16:44:04 Scott Pate wrote:
> This plugin reported a web server I scanned as being vulnerable to SQL
> injection.
We identified the problem and fixed it. It will soon be in the feed.
Thanks.
Note: in your situation, the bug was triggered by optimize_tests=no.
This
configuration is not recommended (and it is slower).
--- Begin Message ---
Hi Scott,
On Jun 10, 2008, at 2:20 PM, Scott Pate wrote:
> Unless I am missing something, it seems there are some options
> missing from the new NessusClient
>
> -Where is the option to enable/disable "optimize test"?
This option is not exposed any more. Given how we code plugins now,
there is no reason why you would want to use it.
> -Where are all of the knowledge base options?
This functionality is not officially supported any more. (you can
always edit the .nessus file directly and change these settings, but
we do not recommend you rely on them).
-- Renaud
--- End Message ---
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
