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
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.
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
I don't think I made my self clear.
We don't have access to the OpenVAS instance, can't run any commands
against it.
As far as I understand the results XML has nothing to do with the OMP or
OAP protocols (but I may be wrong here).
The report is part of the GET_REPORTS command response. So
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.
On Mon, Oct 6, 2014 at 4:31 AM, Matthew Mundell
matthew.mund...@greenbone.net wrote:
I don't think I
Hi Hani,
I don't think I made my self clear.
We don't have access to the OpenVAS instance, can't run any commands
against it.
As far as I understand the results XML has nothing to do with the OMP or
OAP protocols (but I may be wrong here).
We're just parsing the XML produced by OpenVAS,
