-
Notifications
You must be signed in to change notification settings - Fork 743
Rename account_passwords_pam_faillock_audit #9462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename account_passwords_pam_faillock_audit #9462
Conversation
|
I will fix the |
|
@marcusburghardt the rename of a rule will break tailoring for people and will cause troubles for insights |
@jan-cerny , this rule was introduced about just two months ago (2022-06-21). Unfortunately it was merged with this misalignment with other similar rules but since it is pretty fresh, I think the risk of breaking eventual tailoring made this meantime is low and acceptable in favor of keeping the project more organized. If we don't fix it now, it would be much painful to fix in the future, which probably wouldn't happen. Could you give me more details about the impact on insights, please? So I can investigate and recalculate the risk. |
|
The problem is that the Insights generate Ansible Playbooks for rules based on the latest (downstream?) release and if that changes they have a mismatch between set of available rules and set of generated Playbooks. |
|
@marcusburghardt I believe that the action plan here would be:
Am I correct? |
Yes, that is correct @jan-cerny . I plan to update these PRs and documentation soon. |
|
Hi, I plan to resume the work on this PR along the week. |
ee0364b to
b7539aa
Compare
|
I rebased the PR and updated it:
Although the commits ids were changed in favor of better organization after the changes, their contents were not modified beyond the changes described above. |
|
This datastream diff is auto generated by the check Click here to see the full diffNew content has different text for rule 'xccdf_org.ssgproject.content_rule_account_passwords_pam_faillock_audit'.
--- xccdf_org.ssgproject.content_rule_account_passwords_pam_faillock_audit
+++ xccdf_org.ssgproject.content_rule_account_passwords_pam_faillock_audit
@@ -4,6 +4,11 @@
[description]:
PAM faillock locks an account due to excessive password failures, this event must be logged.
+
+[warning]:
+This rule is deprecated in favor of the accounts_passwords_pam_faillock_audit rule.
+Please consider replacing this rule in your files as it is not expected to receive
+updates as of version 0.1.65.
[reference]:
CCI-000044
OVAL for rule 'xccdf_org.ssgproject.content_rule_account_passwords_pam_faillock_audit' differs.
--- oval:ssg-account_passwords_pam_faillock_audit:def:1
+++ oval:ssg-account_passwords_pam_faillock_audit:def:1
@@ -1,9 +1,9 @@
criteria OR
criteria AND
-criterion oval:ssg-test_pam_faillock_audit_parameter_system_auth:tst:1
-criterion oval:ssg-test_pam_faillock_audit_parameter_password_auth:tst:1
-criterion oval:ssg-test_pam_faillock_audit_parameter_no_faillock_conf:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_system_auth:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_password_auth:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_no_faillock_conf:tst:1
criteria AND
-criterion oval:ssg-test_pam_faillock_audit_parameter_no_pamd_system:tst:1
-criterion oval:ssg-test_pam_faillock_audit_parameter_no_pamd_password:tst:1
-criterion oval:ssg-test_pam_faillock_audit_parameter_faillock_conf:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_no_pamd_system:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_no_pamd_password:tst:1
+criterion oval:ssg-test_account_pam_faillock_audit_parameter_faillock_conf:tst:1 |
|
Included |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcusburghardt Thanks for the update. It looks great! Could you please rebase once more because the CentOS stream 9 Testing farm CI job is now fixed so they switched it to required.
Thanks @jan-cerny . Sure, I will rebase it within the next 2 hours. |
This rule was based on a existing rule with similar name: account_passwords_pam_faillock_audit The existing rule name was not aligned to the other similar rules making it prone to confusion. This commit duplicates code but it is worth in order to improve the project consistency. This will be solved in the future by deprecating the rule with inconsistent name.
The accounts_passwords_pam_faillock_audit rule was copied from account_passwords_pam_faillock_audit and both will coexist in the project for some time. Therefore, the OVAL ids used in the deprecated rule were renamed to avoid conflicts while the new rule kept the ids in order to keep consistency with other pam_faillock related rules.
To keep the project more consistent, a new rule was created based on an existing rule but using a name aligned to other similar rules. The old rule can't be removed in short term, but the new rule must replace the old one in control files.
b7539aa to
04a12e3
Compare
Done. |
|
Code Climate has analyzed commit 04a12e3 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 46.5% (0.0% change). View more on Code Climate. |
Description:
All other pam_faillock.so parameters related rules follow a different standard.
It was basically renamed
account_passwords_pam_faillock_audittoaccounts_passwords_pam_faillock_audit.Rationale:
Better sooner than later.