Hi Thomas,
On Saturday 11 September 2010 23:52:49 Thomas Reinke wrote:
>...
> Of course, the general use situation problem here is that if the
> scanner is configured in that mode, and a client then connects
> and expects to get this data back, it would get it.
>
> We (I) like the originally described hack, because it fits
> our usage situation, and it hits the sweet spot of being
> an incredibly trivial patch to implement, with a big pay-off
> in terms of memory reduction. But if we put a patch like
> this together, will anyone else have use for it? I don't like
> having a patched version of the daemon (I'd prefer to be able
> to standardize on the openvassd as officially distributed).
> But I don't like having functionality added to openvassd that
> isn't usable by anyone else, either.
>
> Comments?
I fully support this idea. It is on my roadmap anyway to
cut down the scanner to the absolute minimum.
It is just that you are ahead of us .... we need to
finalize some works on the manager and clients first.
I imagine to have other components take care of the
NVT details managment.
So, please yes, this is a good feature for the 3.2 scanner.
Perhaps we get the act_network feature into a good shape as well.
This would make the next version a big step forward. Once again.
Best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B
202460
Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
