That seems great.
I'm more than interested to help.
Have you selected the target programming language/framework yet?
If you are working on mockups, OmniGraffle-like diagrams or so, please
kindly let me know.
NB: In addition to the OVAL Guidances documents, these lesson learned could help
2015-06-04 10:15 GMT+03:00 Jan Cerny <jcerny(a)redhat.com>:
Nowadays, there is almost no support for OVAL content development.
The developers have to edit the XML files manually, there is no
analysis tool, no debugger or any other tool that could make
the content development faster and easier.
I have started working on a new utility that will be able to
debug OVAL checks, show step-by-step how they are evaluated,
browse collected objects and system characteristics, communicate
with probes, etc.
I'm working on design of the utility now. I'm considering many
alternatives, so I would like to ask you a few questions.
* Can you describe most common problems that you have to face
when you create the OVAL content?
* How do you usually solve these problems?
* Can you tell me an example when did you run into issues with OVAL?
* Imagine an ideal tool for an OVAL developer. What should it be
able to do? What would be its features?
I would appreciate any suggestions, remarks or other inputs.
Thank you very much for your reply.
Security Technologies | Red Hat, Inc.
SCAP Security Guide mailing list