We noticed this error happening after running CIS Hardening, where the umask is changed from 022 to 027 (rule 5.5.4), as stated in #24.
We noticed this error happening after running CIS Hardening, where the umask is changed from 022 to 027 (rule 5.5.4), as stated in #24.