Ensure the Default Bash Umask is Set Correctly *error* Ensure the Default C Shell Umask is Set Correctly *error* Ensure the Default Umask is Set Correctly in /etc/profile *error* Ensure the Default Umask is Set Correctly in login.defs *error* I was pulling out my hair (and I don't have much left anyways) why the umask_bashrc, umask_cshrc, etc were giving the results of "error" during an evaluation. Well, come to find out the variables are typoed, ( user_umask_value instead of umask_user_value) so
cd scap-security-guide/RHEL6/input/profiles perl -pi -e 's/user_umask_value/umask_user_value/' $(grep -Rl user_umask_value *)
fixes that problem.
Yes, that is rather conspicuous, and one wonders how it made it into the test profile without encountering ... testing.
Fixing it now -- thanks!
On 02/05/2013 03:40 PM, Brian Millett wrote:
Ensure the Default Bash Umask is Set Correctly *error* Ensure the Default C Shell Umask is Set Correctly *error* Ensure the Default Umask is Set Correctly in /etc/profile *error* Ensure the Default Umask is Set Correctly in login.defs *error*
I was pulling out my hair (and I don't have much left anyways) why the umask_bashrc, umask_cshrc, etc were giving the results of "error" during an evaluation. Well, come to find out the variables are typoed, ( user_umask_value instead of umask_user_value) so
cd scap-security-guide/RHEL6/input/profiles perl -pi -e 's/user_umask_value/umask_user_value/' $(grep -Rl user_umask_value *)
fixes that problem.
Brian Millett "Shifts in paradigms often cause nose bleeds." Greg Glenn
scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
scap-security-guide@lists.fedorahosted.org