> > Henri, I'm starting to think this info would be better in a host detail > > generated by the Manager. ??So far the OMP handling of host details has been > > completely generic. ??This new detection tag brings the specifics into OMP, > > especially the new product and location children. ??Adding a host detail is > > also more lightweight than extending OMP. ??For OMP we have to extend the > > OMP schema description and sort out the report importing. > > > > What do you think? > > > The lighter the better, of course. > Do you have a suggestion about how to map this information into the > existing host details XML structure? Would you recommend using the > existing detected_at and detected_by entries and add a single host > detail to link result IDs?
I'm kindof OK with DETECTION in RESULT, because that Manager has to special case that because it's creating the result UUIDs. So if we leave that at least that part will be very straight forward for clients. But PRODUCT and LOCATION seem to be doing what the host details are supposed to do. Can the client get these directly from the host details given the NVT OID in the DETECTION? Or is there more too it? I will look at the patch and try understand more clearly. Somewhere in here I'm wondering if we need something like a "result detail", analogous to a "host detail". Like a way for the scanner to pass named info about results over and above the description. Or is the host detail sufficient for this? -- Greenbone Networks GmbH Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460 Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-plugins mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-plugins
