On 11/10/2014 04:43 AM, Daniel Martin wrote: > 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. Hi Daniel
I was just playing with this on Friday to create work tickets in both Service Now and Redmine via API, using extracted XML reports. Currently, I am creating the subject/short description from the first 'name' tag nested under the first 'nvt' tag, and the longer description from the 'tags' tag. In the three sample reports I pulled to work off of, I found that only one of them used the 'description' tag, so i decided it wasn't very reliable and in the one case it was used, contained nearly the same information as the 'tags' tag. It's not very pretty, but seems to be working in my initial testing. cheers, K > 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 > _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
