Bug 1889344 - Rebase scap-security-guide in Red Hat Enterprise Linux 8.4 to latest upstream version
Summary: Rebase scap-security-guide in Red Hat Enterprise Linux 8.4 to latest upstream...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Vojtech Polasek
QA Contact: Matus Marhefka
Jan Fiala
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-19 12:38 UTC by Watson Yuuma Sato
Modified: 2021-05-18 15:54 UTC (History)
7 users (show)

Fixed In Version: scap-security-guide-0.1.54-1.el8
Doc Type: Enhancement
Doc Text:
.SCAP Security Guide rebased to 0.1.54 The `scap-security-guide` packages have been rebased to upstream version 0.1.54, which provides several bug fixes and improvements. Most notably: * The *Operating System Protection Profile* (OSPP) has been updated in accordance with the Protection Profile for General Purpose Operating Systems for Red Hat Enterprise Linux 8.4. * The *ANSSI* family of profiles based on the ANSSI BP-028 recommendations from the French National Security Agency (ANSSI), has been introduced. The content contains profiles implementing rules of the Minimum, Intermediary and Enhanced hardening levels. * The Security Technical Implementation Guide (*STIG*) security profile has been updated, and it implements rules from the recently-released version V1R1.
Clone Of:
Last Closed: 2021-05-18 15:54:34 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Description Watson Yuuma Sato 2020-10-19 12:38:12 UTC
Description of problem:
Update scap-security-guide to latest upstream version.

Comment 29 errata-xmlrpc 2021-05-18 15:54:34 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 (scap-security-guide bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.