Hi, sorry for the late comment, but things keep us extremely busy these days.
On Tuesday 26 June 2012 21:01:00 Matthew Mundell wrote: > > I wonder whether we should take this opportunity and create a section > > <nvts> > > <nvt oid="..."> > > </nvt> > > ... > > </nvts> > > > > into the report and only have references in the results via the OID. > > Then we could add the full NVT information in there always. > > It has the disadvantage of obligating clients to de-refernce inside > > the XML. > > > > How do people here feel about this? > > We'll have to do a bit of work in the Manager to implement this. > > It does sound like a sensible option, but I remember discussing something > similar with you and Henri and we found some drawback. Perhaps that case > was more to do with CVEs. Struggling to find the IRC log. > > And perhaps it would be simpler on the whole to make the client do a > GET_NVTS for each NVT to get the extra info? How common will it be that an > OMP client needs this extra info? one fundamental idea with the inclusion of NVT data into a report is the completeness (in the sense of comprehensibility) of a report as a single document. So, less a client-ability-question. More about what the Report Plugins can do with the results. However, that is all a bigger change. Matt: Do you see any concerns with directly applying Sebastiens' patch with a quick direct help? -- 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/cgi-bin/mailman/listinfo/openvas-devel
