Hide Forgot
Description of problem: When scanning local machine, not ticking "Fetch remote resources", strange warning is printed in the diagnostics window. Version-Release number of selected component (if applicable): scap-workbench-1.1.2-1.el7.x86_64 How reproducible: reliably Steps to Reproduce: 1. start scap-workbench 2. select for example pci-dss profile 3. scan machine without ticking "Fetch remote resources" Actual results: In diagnostics window, warning is printed: Error when parsing scan progress output from stdout of the 'oscap' process. Newline encountered while reading rule ID, rule result and/or ':' are missing! Read buffer is 'This content points out to the remote resources. Use `--fetch-remote-resources' option to download them.'. Expected results: Fetch this expected line, and print out warning with user-friendly explanation, for example 'Remote resources might be necessary for this profile to work properly. Please select "Fetch remote resources" for complete scan.' Additional info:
Fixed upstream in https://github.com/OpenSCAP/scap-workbench/pull/82 and https://github.com/OpenSCAP/openscap/pull/540
Verified fix on version: [dahaic@localhost ~]$ rpm -qa scap-workbench scap-workbench-1.1.4-4.el7.x86_64 [dahaic@localhost ~]$ rpm -qa openscap-scanner openscap-scanner-1.2.14-2.el7.x86_64 When scanning profile with remote resources requirement, diagnosis window now shows no error, and these two warnings: 13:37:50 warning Remote resources might be necessary for this profile to work properly. Please select "Fetch remote resources" for complete scan 13:37:50 warning Skipping https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 file which is referenced from XCCDF content When fetch remote resources is checked, it currently fails, depending on scap-security-guide version. It is a regression, but not due to update of scap-workbench, but because of ssg. So created a new Bug 1456429
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:2296