Bug 1703010

Summary: Remediation for ensure_gpgcheck_repo_metadata prevents packages installation and the rule has been dropped from recommendations
Product: Red Hat Enterprise Linux 7 Reporter: Gabriel Gaspar Becker <ggasparb>
Component: scap-security-guideAssignee: Gabriel Gaspar Becker <ggasparb>
Status: CLOSED ERRATA QA Contact: Watson Yuuma Sato <wsato>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.6CC: ggasparb, mhaicman, openscap-maint, wsato
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.43-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:04:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gabriel Gaspar Becker 2019-04-25 10:02:22 UTC
Description of problem:
Remediation for rule ensure_gpgcheck_repo_metadata prevents the system from installing packages. This rule has been dropped by DISA STIG recommendations and needs to be removed from profiles which contains it.

Needs to be removed from profiles such as:
ospp
hipaa
stig-rhel7-disa

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.40-12.el7.noarch

How reproducible:
100%


Steps to Reproduce:
1. cat /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml | grep ensure_gpgcheck_repo_metadata | grep selected=\"true\"
2.
3.

Actual results:
Rule is selected by specified profiles

Expected results:
Rule is not selected by specified profiles

Additional info:

Comment 6 errata-xmlrpc 2019-08-06 13:04:20 UTC
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-2019:2198