Am Mittwoch, 1. Oktober 2014, 15:51:43 schrieb Geoff Galitz: > FWIW, openvas as a wrapper around other established tools/projects is half > the point of openvas (to me anyways). It would be great if the project > somehow identifies what needs to be done to get these to work again. > There's no real reason the appropriate scripts/configs cannot be edited or > added.. just lack of develpment resources.
While I think it is very valuable to have various scan tools managed via OpenVAS I think it is the wrong appoach to wrap up other tools within a NASL NVT. Which is something that OpenVAS inherited. This approach causes several headaches. This topic was discussed at the last OpenVAS developer conferences and meanwhile we have started a prototype for the new OSP concept (OpenVAS Scanner Protocol). w3af serves as a reference for this. We are not yet where we want to be. But OpenVAS-8 will likely offer something usable. Please be patient with our limited development resources. We have a couple of open developer positions at Greenbone btw ;-) I also can offer to sponsor any OSP wrapper development for the various other scan tools. You need to be familiar with trunk and Python for this. -- 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-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
