-
Notifications
You must be signed in to change notification settings - Fork 760
Add new rule accounts_passwords_pam_faillock_unlock_time_with_zero #14188
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
Conversation
Add new rule `accounts_passwords_pam_faillock_unlock_time_with_zero` which is almost the same as `accounts_passwords_pam_faillock_unlock_time`, but it allows the `unlock_time` faillock parameter to be set either to zero or to value greater than the value of the `var_accounts_passwords_pam_faillock_unlock_time` variable. By allowing also 0, we better align with the requirement 5.3.2.1.2 of the RHEL 10 CIS Benchmark v1.0.1. Resolves: https://issues.redhat.com/browse/OPENSCAP-6095
...t_password_attempts/accounts_passwords_pam_faillock_unlock_time_with_zero/ansible/shared.yml
Show resolved
Hide resolved
| @@ -0,0 +1,6 @@ | |||
| # platform = multi_platform_all | |||
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.
Missing shebang
|
|
||
| <!-- pam_faillock.so parameters can be defined directly in pam files or, in newer | ||
| versions, in {{{ pam_faillock_conf_path }}}. The last is the recommended option when | ||
| available. Also, is the option used by auselect tool. However, regardless the |
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.
| available. Also, is the option used by auselect tool. However, regardless the | |
| available. Also, is the option used by authselect tool. However, regardless the |
|
@jan-cerny: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
I have fixed shebangs and typo |
Add new rule
accounts_passwords_pam_faillock_unlock_time_with_zerowhich is almost the same asaccounts_passwords_pam_faillock_unlock_time, but it allows theunlock_timefaillock parameter to be set either to zero or to value greater than the value of thevar_accounts_passwords_pam_faillock_unlock_timevariable. By allowing also 0, we better align with the requirement 5.3.2.1.2 of the RHEL 10 CIS Benchmark v1.0.1.Resolves: https://issues.redhat.com/browse/OPENSCAP-6095