[Open-scap] picture

[Peter Vrabec]

Hi Kevin,


> lib_openSCAP.OVAL provides something along the lines of:
> structs:
> OvalDefinition
> OvalTest
> OvalCriterion
> OvalObject
> OvalState
> OvalTestResult
> etc.
> functions:
> load_definitions
> export_characteristics
> export_results
> ProbeObject
> ResolveTest
> etc.
>
> In other words, the only tweak I would propose to the architecture you've
> defined is moving the directly OVAL related capabilities within scap_daemon
> down into the OVAL library within lib_openscap while leaving the higher
> level functionality of actually staying memory resident, monitoring for
> incoming signals, sending results to a server and other such facilities to
> scap_daemon which is basically our prototype for an app that would live in
> that top layer (what I believe Net-Centric folks like to call the
> "utilization layer").
>
> What do you think?
It makes sense to me. Thanks to make this clear, because I was in confusion 
that you want only load,export after one of the previous meetings. :)

Does anyone works on lib_openSCAP.OVAL from your  side? I'm asking because 
Tomas Heinrich works on structs for oval definition file.


Peter.