Bug 2050232 - Rule password_set_min|max_life_existing failing.
Summary: Rule password_set_min|max_life_existing failing.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: openscap
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 2059300
TreeView+ depends on / blocked
 
Reported: 2022-02-03 14:02 UTC by Achilleas Yfantis
Modified: 2023-08-03 07:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2059300 (view as bug list)
Environment:
Last Closed: 2023-08-03 07:28:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OPENSCAP-3507 0 None None None 2023-07-11 12:14:06 UTC
Red Hat Issue Tracker RHELPLAN-111000 0 None None None 2022-02-03 14:04:59 UTC

Description Achilleas Yfantis 2022-02-03 14:02:23 UTC
Description of problem:

Rule: password_set_min|max_life_existing fails during regression when testing: stig profile remediations


Version-Release number of selected component (if applicable):

openscap: 1:1.3.5-13.el9
scap-security guide: 0.1.61-1.git935a955.el9

How reproducible:

every time


Steps to Reproduce:
1.Have a rhel-9 machine
2.Run the stig profile

Actual results:

rules failing

Expected results:

rules passing


Additional info:
This issue has been noted again in this issue: https://github.com/ComplianceAsCode/content/pull/8107
After a discussion its related with the order of the rule execution.
Issue has also been reported on github here: https://github.com/ComplianceAsCode/content/issues/8144

Comment 7 RHEL Program Management 2023-08-03 07:28:35 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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