-
The -v flag for verbose output seems to be set regardless of whether the user provides the flag or not. My guess is that things like the OVALDI output should only be shown in verbose mode.
2009-11-19 15:03:46 UTC in XCCDF Interpreter
-
Can we have the output of the tool display the individual rule results in the command window? Currently these results are only given in the result XML file.
2009-11-19 15:00:08 UTC in XCCDF Interpreter
-
For both XCCDF Rules and XCCDF Groups, the specification outlines a 'conflicts' attribute. Support for this is missing in the reference implementation and needs to be added.
2009-09-18 14:10:37 UTC in XCCDF Interpreter
-
rework the selection support.
2009-09-18 14:08:38 UTC in XCCDF Interpreter
-
support Loading.Noticing and Loading.Resolve.Items.
2009-09-18 14:08:14 UTC in XCCDF Interpreter
-
In order to support new checking systems in the future, we need to design a pluggable checking system capability. Currently, only the OVAL checking system is supported. In the short term, there is a need to integrate the OCIL checking system. This is a great time to design a new pluggable capability.
2009-09-18 14:07:45 UTC in XCCDF Interpreter
-
support for cluster-ids within XCCDF Items.
2009-09-18 14:04:35 UTC in XCCDF Interpreter
-
enable XCCDF Rule selectivity.
2009-09-18 14:04:14 UTC in XCCDF Interpreter
-
The XCCDF Specification does not mandate the existence of a Profile, yet the current code requires a Profile to inorder to process a document. This dependency needs to be removed.
2009-09-18 14:03:45 UTC in XCCDF Interpreter
-
The XCCDF Specification spells out the notion of XCCDF Item extension. This needs to be added to this reference implementation.
2009-09-18 14:01:52 UTC in XCCDF Interpreter
