On Friday 20 March 2009 13:37:11 John A. Sullivan III wrote:
> I'm quite keen to do that and my scripts have almost all been modified.
> However, I would I know this worked? Do I count the plugin lines in the
> rc file before and after running? Do I delete all the plugin lines in
> the rc file before running and see if anything at all is run?
Sounds good to me.
1) Move some scripts away on server side,
2) rebuild the cache (delete the cache files .desc, restart server).
3) Get a coffee.
4) Remove plugin lines in clients rc.
5) Scan.
6) Backup rc file of client.
7) On server, move scripts back.
8) Ensure that cache is rebuild (restart server, verify by looking for 
new .desc s).
9) Scan.
10) Compare rc against back-uped one and especially look for new enabled 
plugins.

> Alas, I am ignorant of the OpenVAS internals and sorely pressed for time
> on the overall project of which this is just a part (hence can't take
> much time right now to learn the internals).  I'll gladly share the
> results once I know how to test.  Thanks - John

Thats a pity, we all hope that it will change soon :)

-- felix

>
> On Fri, 2009-03-20 at 11:07 +0100, Felix Wolfsteller wrote:
> > "auto_enable_new_plugins" will switch new plugins on or off. In order to
> > _get_ new plugins (wich, afaik are always added to the rc) you have to
> > reconnect. As with the cron-job and the CLI you are freshly connecting
> > each time you start a scan, that should be ensured.
> > But I am not 100% sure that the "auto_enable_new_plugins" comes into
> > effect when using the CLI.
> > Would be nice if you report that (or if) it works.
> >
> > --felix
> >
> > On Friday 20 March 2009 10:51:23 John A. Sullivan III wrote:
> > > That would be fabulous and so much simpler.  So the plugins do not need
> > > to be listed in the rc file first? I was ignorantly assuming that would
> > > merely change the status from no to yes but then those wouldn't be new
> > > plugins, would they! Thanks - John
> > >
> > > On Fri, 2009-03-20 at 09:27 +0530, Chandrashekhar B wrote:
> > > > Hello John,
> > > >
> > > > I think, adding "auto_enable_new_plugins = yes" should do the job in
> > > > the rc file.
> > > >
> > > > Chandra.
> > > >
> > > > -----Original Message-----
> > > > From: [email protected]
> > > > [mailto:[email protected]] On Behalf Of
> > > > John A. Sullivan III
> > > > Sent: Friday, March 20, 2009 1:36 AM
> > > > To: [email protected]
> > > > Subject: [Openvas-discuss] updaterc script?
> > > >
> > > > Hello, all.  We are delighted that, after tracking down a pile of
> > > > dependencies, our CentOS 5.2 based automated vulnerability scanning
> > > > server is running on OpenVAS.  However, it is automated and runs
> > > > scans from cron jobs calling OpenVAS-Client in batch mode.  Thus,
> > > > updating the rc files with the latest plugins is a problem.
> > > >
> > > > Is there an OpenVAS equivalent of the various update-nessusrc scripts
> > > > we used to use under Nessus? Thanks - John


-- 
Felix Wolfsteller |  ++49-541-335 08 3451  |  http://www.intevation.de/
PGP Key: 39DE0100
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to