<table><tbody><tr class="result-error"><td class="id"><a>Ensure the Default Bash Umask is Set Correctly</a>
</td>
<td class="result">
<strong class="strong">error</strong>
</td>
</tr>
<tr class="result-error">
<td class="id">
<a>Ensure the Default C Shell Umask is Set Correctly</a>
</td>
<td class="result">
<strong class="strong">error</strong>
</td>
</tr>
<tr class="result-error">
<td class="id">
<a>Ensure the Default Umask is Set Correctly in /etc/profile</a>
</td>
<td class="result">
<strong class="strong">error</strong>
</td>
</tr>
<tr class="result-error">
<td class="id">
<a>Ensure the Default Umask is Set Correctly in login.defs</a>
</td>
<td class="result">
<strong class="strong">error</strong></td></tr></tbody></table><br>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<br>
<br>cd scap-security-guide/RHEL6/input/profiles<br>perl -pi -e 's/user_umask_value/umask_user_value/' $(grep -Rl user_umask_value *)<br clear="all"><br>fixes that problem.<br>-- <br>Brian Millett <br> "Shifts in paradigms<br>
often cause nose bleeds."<br>Greg Glenn