Bug 1564902

Summary: Rebase scap-security-guide in Red Hat Enterprise Linux 7.6 to latest upstream version
Product: Red Hat Enterprise Linux 7 Reporter: Marek Haicman <mhaicman>
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Marek Haicman <mhaicman>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: jflemer, matyc, mhaicman, mmarhefk, mpreisle, mthacker, openscap-maint
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:46:47 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:

Description Marek Haicman 2018-04-08 18:57:15 UTC
SCAP-Security-Guide (SSG) contains configuration hardening advice of Red Hat  Enterprise Linux 7 and other products. Some customers are contributing fixes  directly to upstream. The expectation is that we ship these fixes/improvements along the RHEL update release.

There has been significant changes to the build system / data structure in the upstream project, making non-rebase backports difficult and error prone.

The version currently in RHEL7 is 0.1.36, https://github.com/OpenSCAP/scap-security-guide/compare/v0.1.36...master shows changes in upstream since then.

Comment 4 Matěj Týč 2018-07-26 11:40:10 UTC
*** Bug 1608736 has been marked as a duplicate of this bug. ***

Comment 5 Marek Haicman 2018-09-26 09:57:28 UTC
Verified that version scap-security-guide-0.1.40-12.el7 has no regressions is major functionality.

Comment 7 errata-xmlrpc 2018-10-30 11:46:47 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-2018:3308