In addition to what is already mentioned below, in terms of documentation, I'd recommend to simply read through the docs that exist and make any changes you think would be helpful. That's pretty much what I do.
There was a request to add some documentation about how the client cache works, though. Some examples of real world deployments would be helpful too, I think. Things like what OS OpenVAS is deployed on, how many nodes are being scanned, what kind of nodes and what happens afterwards... if your security policy allows posting of that kind of information. Anyways... feel free to just jump in and ask questions. We're a friendly and easy going bunch. -geoff --------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/ > -----Original Message----- > From: [email protected] [mailto:openvas-discuss- > [email protected]] On Behalf Of Felix Wolfsteller > Sent: Freitag, 28. August 2009 11:29 > To: [email protected] > Subject: Re: [Openvas-discuss] first post > > Hi John, > great offer! > Just came to my mind: > > * Jan mentioned the manpage for openvas-nvt-sync is missing (not really > sure > if we need one). > * Apparently the compendium lacks proper documentation of the > "batch"/"CLI" > mode in client ( -q ...). Also the new options when generating reports > (see > CHANGES) are not mentioned in the clients manpage yet. > > Regards > Felix > > On Friday 28 August 2009 11:20:43 Tim Brown wrote: > > On Friday 28 August 2009 07:10:17 Jan-Oliver Wagner wrote: > > > Hi, > > > > > > On Friday 28 August 2009 05:37:44 J W wrote: > > > > I just started using openvas after using nessus for many years. My > > > > nessus install at work is aging so I am moving over to Openvas. I .... _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
