Bug 2158404 - Rebase SSG to the latest upstream version in RHEL 8.8
Summary: Rebase SSG to the latest upstream version in RHEL 8.8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Milan Lysonek
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks: 2168079 2168080 2168081
TreeView+ depends on / blocked
 
Reported: 2023-01-05 10:37 UTC by Watson Yuuma Sato
Modified: 2023-06-27 20:24 UTC (History)
8 users (show)

Fixed In Version: scap-security-guide-0.1.66-2.el8
Doc Type: Enhancement
Doc Text:
.SCAP Security Guide rebased to 0.1.66 The SCAP Security Guide (SSG) packages have been rebased to upstream version 0.1.66. This version provides various enhancements and bug fixes, most notably: * Updated RHEL 8 STIG profiles * Deprecated rule `account_passwords_pam_faillock_audit` in favor of `accounts_passwords_pam_faillock_audit`
Clone Of:
: 2168079 2168080 2168081 (view as bug list)
Environment:
Last Closed: 2023-05-16 08:39:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:
jafiala: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-144007 0 None None None 2023-01-05 10:42:25 UTC
Red Hat Product Errata RHBA-2023:2869 0 None None None 2023-05-16 08:40:08 UTC

Description Watson Yuuma Sato 2023-01-05 10:37:07 UTC 
Update scap-security-guide in RHEL to the latest upstream version.
Comment 20 errata-xmlrpc 2023-05-16 08:39:41 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.

https://access.redhat.com/errata/RHBA-2023:2869
Note You need to log in before you can comment on or make changes to this bug.