You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In rule accounts_umask_etc_bashrc on Fedora or RHEL the "/etc/bashrc" is configured but on other systems eg. Debian 12 the name of the file is "/etc/bash.bashrc". It seems to be the case also for SLES. We don't always use the correct file path. That causes for example Automatus fail on Debian 12. We need to ensure that rule.yml, all checks and remediations and also all test scenarios use a correct file path depending on platform.
SCAP Security Guide Version:
current upstream master as of HEAD da1fa23 as of 2024-09-20
Operating System Version:
all
Steps to Reproduce:
review accounts_umask_etc_bashrc
Actual Results:
wrong file path used on Debian 12
Expected Results:
rule.yml, all checks and all remediations and also all test scenarios use a correct file path
Additional Information/Debugging Steps:
no
The text was updated successfully, but these errors were encountered:
Description of problem:
In rule accounts_umask_etc_bashrc on Fedora or RHEL the "/etc/bashrc" is configured but on other systems eg. Debian 12 the name of the file is "/etc/bash.bashrc". It seems to be the case also for SLES. We don't always use the correct file path. That causes for example Automatus fail on Debian 12. We need to ensure that rule.yml, all checks and remediations and also all test scenarios use a correct file path depending on platform.
SCAP Security Guide Version:
current upstream master as of HEAD da1fa23 as of 2024-09-20
Operating System Version:
all
Steps to Reproduce:
Actual Results:
wrong file path used on Debian 12
Expected Results:
rule.yml, all checks and all remediations and also all test scenarios use a correct file path
Additional Information/Debugging Steps:
no
The text was updated successfully, but these errors were encountered: