Hide Forgot
+++ This bug was initially created as a clone of Bug #1312824 +++ Description of problem: I am not able to reference oval file via absolute path. xccdf / check / check-content-ref / href is of type anyURI, which is defined in RFC 2396 ( https://www.ietf.org/rfc/rfc2396.txt ). Thus it should support file://<abs-path> Version-Release number of selected component (if applicable): openscap-1.2.5-3.el7 How reproducible: reliably Steps to Reproduce: 1. reference oval file with absolute path 2. oscap xccdf eval $xccdf Actual results: WARNING: Skipping /tmp/tmp.oBlqLIiXmD/file://tmp/tmp.oBlqLIiXmD/oval.xml file which is referenced from XCCDF content Expected results: /tmp/tmp.oBlqLIiXmD/oval.xml is used properly Additional info:
Upstream fix proposed: https://github.com/OpenSCAP/openscap/pull/645
Verified. [0 root@qeos-145 unittests]# rpm -qa openscap openscap-1.2.14-1.el7.x86_64 TEST: Load OVAL using absolute path /tmp/tmp.sU3BguZDfN ~/rpmbuild/BUILD/openscap-1.2.14/tests/API/XCCDF/unittests Stderr file = /tmp/test_xccdf_oval_absolute_path.err.gjJV2U Result file = /tmp/test_xccdf_oval_absolute_path.out.result.3B81oh Report file = /tmp/test_xccdf_oval_absolute_path.out.report.pq8862 Title Rule xccdf_moc.elpmaxe.www_rule_1 Result pass Title Rule xccdf_moc.elpmaxe.www_rule_2 Result pass OVAL Results are exported correctly. XCCDF Results are exported correctly. ~/rpmbuild/BUILD/openscap-1.2.14/tests/API/XCCDF/unittests /tmp/tmp.Qmuvjc4pfL ~/rpmbuild/BUILD/openscap-1.2.14/tests/API/XCCDF/unittests Stderr file = /tmp/test_xccdf_oval_absolute_path.err.75u4x1 Result file = /tmp/test_xccdf_oval_absolute_path.out.result.akfzZS Report file = /tmp/test_xccdf_oval_absolute_path.out.report.5cIVT0 Title Rule xccdf_moc.elpmaxe.www_rule_1 Result pass Title Rule xccdf_moc.elpmaxe.www_rule_2 Result pass OVAL Results are exported correctly. XCCDF Results are exported correctly. ~/rpmbuild/BUILD/openscap-1.2.14/tests/API/XCCDF/unittests RESULT: PASSED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2291