On Montag, 1. September 2008, Chandrashekhar B wrote:
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jan-Oliver
> Wagner
> Sent: Monday, September 01, 2008 7:15 PM
> To: openvas-devel@wald.intevation.org
> Subject: Re: [Openvas-devel] OpenVAS plugins standardization
>
> On Montag, 1. September 2008, Chandrashekhar B wrote:
> > > well, the printed report should not necessarily contain all of this.
> > > Even the GUI client should allow it configurable whether
> > > to manage these information.
> >
> > By looking at logs and the KB items store, we can make out why a plugin
> > isn't launched. In any case, it would be better if there's a single
> location
> > where we can look through to identify failed instances. Instead of
> clogging
> > the reports, can we redirect these to a log and debug file?
>
> > a major concern of mine is that with the current concept you
> > have the OpenVAS-Client running and right next to it a root
> > shell to the openvas-server installation.
> > OK, you can configure things for non-root, but after all it is a bit
> > strange to always accompany the GUI client with a shell ...
>
> My concern is about not being able to separate data that reports
> vulnerabilities against data that is aiding us to analyze. Reports can
> become huge with number of notes such as,
>
> Application not installed, service not installed, port not open...
very true.
> If there's an option to separate, it is good.
we have to find a way to allow for both needs.
Some configure options to switch on/off verbosity is
the way to go, I guess. I am open regarding the default config ;-)
Best
Jan
--
Dr. Jan-Oliver Wagner Intevation GmbH, Osnabrück
Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
