I think I finally found what is happening and can recreate it each
time(right or wrong). Create a empty policy to scan for only 10863 in
the GUI. Scan runs perfect every time. Export that policy to a file and
it fails to provide results every time. Regardless of what plugins are
turned on in the PLUGIN_SET, it will continue to fail each time.

After adding the section SCANNER_SET, but leaving it completely empty,
the scan runs and provides accurate results. During the scan it appears
that Nessus adds plugins to that SCANNER_SET that were not there before.
I assume without a SCANNER_SET section at all Nessus is unable to add
these during the scan and is why it was failing. Here is what my
SCANNER_SET looks like after the scan completed but again, was empty
when it started.

begin(SCANNER_SET)
 11840 = yes
 10796 = yes
 10335 = yes
 14272 = yes
 14274 = yes
 11219 = yes
 10180 = yes
end(SCANNER_SET)


Danny






-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mallory, Danny
Sent: Saturday, October 20, 2007 11:51 AM
To: [EMAIL PROTECTED]; [email protected]
Subject: Re: Nessus client policy export


I had tested several new working scan policies to only gather ssl certs
in the gui. When exported and ran with command line I would get no
results untill I added a scanner-set to the export.  I did doublecheck
and I'd 10863 was in the plugin set as yes and dependencies was on also.
After adding scanner_set it returned results.



----- Original Message -----
From: Renaud Deraison <[EMAIL PROTECTED]>
To: Nessus List <[email protected]>
Cc: Mallory, Danny
Sent: Sat Oct 20 09:53:21 2007
Subject: Re: Nessus client policy export


On Oct 20, 2007, at 4:32 PM, Mallory, Danny wrote:

>
> Is there a reason that the export policy in Nessus Client does not
> create a section for the "SCANNER_SET".. Only PLUGIN_SET is created
> and nothing gets scanned.. By manually inserting a SCANNER_SET above
> the PLUGIN_SET fixes it.
SCANNER_SET and PLUGIN_SET really are the same thing internally -- as
long as the plugin ID of the scanners is in the PLUGIN_SET section, then
they will get enabled and the scan will proceed.


                                        -- Renaud


______________

The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete
the message and all copies; (ii) do not disclose, distribute or use the
message in any manner; and (iii) notify the sender immediately. In
addition, please be aware that any message addressed to our domain is
subject to archiving and review by persons other than the intended
recipient. Thank you.

_____________


______________

The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.

_____________
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to