Hi,
Just revisiting this to do our implementation.
Whilst a XSD would be desirable and probably the end goal, making the
version (either the OMP version or the OpenVAS version) part of the
<result> XML would serve just as well and shouldn't take long. Maybe as
an attribute of <report> or a nested tag.
It doesn't look like we currently have many options, so for now we're
going to inspect the contents of the <tags> item of the first
"/report/results/result" to try to detect the "summary=" string
(indicating OMPv5 / OpenVASv7) or the <description> tag to detect the
"Summary:" string (indicating OMPv4 / OpenVASv6). But this seems like a
very brittle implementation.
Thanks for you help everyone, and if someone has a better implementation
idea, I'd love to hear it!
Cheers,
Daniel
Jan-Oliver Wagner wrote:
Am Montag, 6. Oktober 2014, 15:15:33 schrieb Brandon Perry:
TBH there should be a published XSD of the XML report so that programs can
validate the reports they are getting against them, and so that multiple
versions of the reports can be supported.
I agree it is desirable.
Currently we are lacking man power to solve this quickly (we have open positions
at Greenbone btw).
However, once we get to the Import Center feature it will be worked on for sure.
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
