Currently it's not possible the shorthand form of OVAL definition to contain
<ind:variable_object> definition (based on previously defined
The reason behind this limitation being that idtranslate.py script
(which is internally
called by relabelids.py script, which is subsequently called during the
build process) is not currently able to properly handle <ind:var_ref>
When translating the OVAL ids idtranslate.py is able to correctly
replace value of
'var_ref' attribute, but not able to translate the id when 'var_ref'
isn't an attribute,
but rather an tag / element directly. The <variable_object> definition
the form of:
<ind:variable_object id="object_id" version="1">
Since (currently) value of <ind:var_ref> element isn't properly
real ID, during the benchmark build process the error like the following
... [pattern] id 'variable_name' does not meet the expected pattern
This results in unability to successfully build the benchmark, when
(containing by xsd required reference to var_ref) is used.
Since I need the capability to define variable_objects (see the patch
idtranslate.py script (in RHEL/6 and also across the content) to be able
handle variable_objects (properly translate var_ref ids even in case
it's listed as tag / element).
The function / proper work of proposed change is confirmed by successful
of subsequent patch (see patch [2/2] for further details).
Thank you && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Technologies Team