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
on a server that store a massive number of files in a data directory, I want to exclude that data filesystem from being run through by hardening scripts, especially find commands, as it can take literally hours and impact disk accesses.
This is currently possible with configuration variables, however it takes 3 different variables to fullfill that need: EXCEPTIONS for rule 1.1.21, EXCLUDED for rules 6.1.10, 6.1.11 and 6.1.12 and IGNORED_PATH for rules 6.1.13 and 6.1.14
Please also note that rules 4.2.1.4, 5.4.2, 6.1.13, 6.1.14, 6.2.6, 6.2.8, 6.2.9, 6.2.16 have a different meaning for the EXCEPTIONS variable, making impossible to set this variable globally.
These inconsistencies should be corrected to have a unique variable accross all scripts to exclude a path/filesystem from all scripts.
The text was updated successfully, but these errors were encountered:
sblaisot
changed the title
gnoring path requires 3 different variables
Ignoring path requires 3 different variables
Feb 5, 2024
on a server that store a massive number of files in a data directory, I want to exclude that data filesystem from being run through by hardening scripts, especially find commands, as it can take literally hours and impact disk accesses.
This is currently possible with configuration variables, however it takes 3 different variables to fullfill that need:
EXCEPTIONS
for rule1.1.21
,EXCLUDED
for rules6.1.10
,6.1.11
and6.1.12
andIGNORED_PATH
for rules6.1.13
and6.1.14
Please also note that rules
4.2.1.4
,5.4.2
,6.1.13
,6.1.14
,6.2.6
,6.2.8
,6.2.9
,6.2.16
have a different meaning for theEXCEPTIONS
variable, making impossible to set this variable globally.These inconsistencies should be corrected to have a unique variable accross all scripts to exclude a path/filesystem from all scripts.
The text was updated successfully, but these errors were encountered: