Hide Forgot
+++ This bug was initially created as a clone of Bug #1401911 +++ Description of problem: Client variant of Red Hat Enterprise Linux 7, is not recognized as RHEL by OVAL rules in CPE definitions shipped with SSG. Thus scanning on this variant would produce meaningless results. Version-Release number of selected component (if applicable): scap-security-guide-0.1.30-3.el7.noarch How reproducible: reliably Steps to Reproduce: 1. oscap oval eval /usr/share/xml/scap/ssg/content/ssg-rhel6-cpe-oval.xml Actual results: Definition oval:ssg-installed_OS_is_rhel7:def:1: false Expected results: Definition oval:ssg-installed_OS_is_rhel7:def:1: true Additional info:
Fix merged upstream this morning: https://github.com/OpenSCAP/scap-security-guide/pull/1702
Verified. NEW: :: [ LOG ] :: Package versions: :: [ LOG ] :: scap-security-guide-0.1.33-1.el7.noarch :: [ PASS ] :: Command 'rpm -e --nodeps redhat-release-server-7.3-4.el7.x86_64' (Expected 0, got 0) :: [ PASS ] :: Command 'rpm -i rpms/RHEL7/redhat-release-client-*.x86_64.rpm' (Expected 0, got 0) :: [ PASS ] :: Command 'oscap oval eval /usr/share/xml/scap/ssg/content/ssg-rhel7-cpe-oval.xml > output' (Expected 0, got 0) :: [ INFO ] :: Current redhat-release is redhat-release-client-7.3-4.el7.x86_64 :: [ INFO ] :: Result: Definition oval:ssg-installed_OS_is_rhel7:def:1: true :: [ PASS ] :: client is supported OLD: :: [ LOG ] :: Package versions: :: [ LOG ] :: scap-security-guide-0.1.30-3.el7.noarch :: [ PASS ] :: Command 'rpm -e --nodeps redhat-release-server-7.3-4.el7.x86_64' (Expected 0, got 0) :: [ PASS ] :: Command 'rpm -i rpms/RHEL7/redhat-release-client-*.x86_64.rpm' (Expected 0, got 0) :: [ PASS ] :: Command 'oscap oval eval /usr/share/xml/scap/ssg/content/ssg-rhel7-cpe-oval.xml > output' (Expected 0, got 0) :: [ INFO ] :: Current redhat-release is redhat-release-client-7.3-4.el7.x86_64 :: [ INFO ] :: Result: Definition oval:ssg-installed_OS_is_rhel7:def:1: false :: [ FAIL ] :: client is not covered by CPE definition
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:2064