On Monday 09 May 2011 10:06:58 Henri Doreau wrote:
> > The NASL code is also less error prone. And keeping things in NASL keeps
> > the core of the Scanner simpler -- keeps the most important part smaller
> > and easier to work with.
> >
> My patch is very similar to the existing C plugins. It's integrated
> within the scanner but is actually far from being intrusive. A single
> new function is exported to NASL, with everything implemented in a
> single C module.
A NASL-based implementation might or might not be superior to
the C-based implementation. But since it is a very lean API of a single function
and only used by a single NVT, it is possible to seamless
switch to a NASL-based implementation any time later on.
I'd prefer to collect more needs on XML capabilities in NASL before
starting some implementations. And we should do so apart from this CR.
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
