Implement rules for /etc/security/opasswd permissions #12693
Conversation
New rules: - file_groupowner_etc_security_opasswd - file_owner_etc_security_opasswd - file_permissions_etc_security_opasswd - file_groupowner_etc_security_opasswd_old - file_owner_etc_security_opasswd_old - file_permissions_etc_security_opasswd_old Note: The Ubuntu 24.04 CIS v1 recommendation 7.1.10 requires ownership and permissions to be set on both opasswd and opasswd.old. The existing rule `file_etc_security_opasswd` satisfies half of the requirement, but, since the implementation is not consistent with other similar rules (not using template or tests), both requirements were implemented as new rules instead.
|
Hi @mpurg. Thanks for your PR. I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
Code Climate has analyzed commit 867ef8d 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 60.9% (0.0% change). View more on Code Climate. |
Description:
Rationale:
file_etc_security_opasswdsatisfies half of the requirement, but, since the implementation is not consistent with other similar rules (not using template or tests), both requirements were implemented as new rules instead of extending the existing rule.