We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The test for the group of /etc/gshadow- fails if group is shadow and not root under Ubuntu 24.04
Title Verify Group Who Owns Backup gshadow File Rule xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_gshadow Result fail
Title Verify Group Who Owns Backup gshadow File Rule xccdf_org.ssgproject.content_rule_file_groupowner_backup_etc_gshadow Result pass
Maybe the difference in the var-handling in https://github.com/ComplianceAsCode/content/blob/f291b6ef20991421d5766dca7e5fcc343fb1036f/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml (static) and
content/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml
Lines 53 to 55 in f291b6e
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description of problem:
The test for the group of /etc/gshadow- fails if group is shadow and not root under Ubuntu 24.04
SCAP Security Guide Version: Nightly Build
Operating System Version: 24.04.1 LTS (Noble Numbat)
Steps to Reproduce:
Actual Results:
Expected Results:
Notes
Maybe the difference in the var-handling in https://github.com/ComplianceAsCode/content/blob/f291b6ef20991421d5766dca7e5fcc343fb1036f/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_gshadow/rule.yml (static) and
content/linux_os/guide/system/permissions/files/permissions_important_account_files/file_groupowner_backup_etc_shadow/rule.yml
Lines 53 to 55 in f291b6e
The text was updated successfully, but these errors were encountered: