Blame SOURCES/scap-security-guide-0.1.37-fix-umask_for_daemons.patch

df3ea4
From 810c6774166d8b591300322e269acd6a1d3554ef Mon Sep 17 00:00:00 2001
df3ea4
From: =?UTF-8?q?Jan=20=C4=8Cern=C3=BD?= <jcerny@redhat.com>
df3ea4
Date: Tue, 5 Dec 2017 16:15:46 +0100
df3ea4
Subject: [PATCH] RHBZ #1520493: Fix umask_for_daemons
df3ea4
df3ea4
OpenSCAP evaluated this rule as "error" because it tried to evauluate
df3ea4
the variable 'var_umask_for_daemons_umask_as_number', which was defined
df3ea4
as external, but in fact is created in other definition. OpenSCAP
df3ea4
could not find its value. The fix is very similar to PR #1945.
df3ea4
---
df3ea4
 shared/checks/oval/umask_for_daemons.xml | 8 ++------
df3ea4
 1 file changed, 2 insertions(+), 6 deletions(-)
df3ea4
df3ea4
diff --git a/shared/checks/oval/umask_for_daemons.xml b/shared/checks/oval/umask_for_daemons.xml
df3ea4
index 7f54e4957..a8ce76275 100644
df3ea4
--- a/shared/checks/oval/umask_for_daemons.xml
df3ea4
+++ b/shared/checks/oval/umask_for_daemons.xml
df3ea4
@@ -61,12 +61,6 @@
df3ea4
     </arithmetic>
df3ea4
   </local_variable>
df3ea4
 
df3ea4
-  
df3ea4
-       the referenced 'var_umask_for_daemons_as_number' OVAL definition -->
df3ea4
-  
df3ea4
-  comment="Required umask converted from string to octal number"
df3ea4
-  datatype="int" version="1"/>
df3ea4
-
df3ea4
   
df3ea4
   comment="Test the retrieved /etc/init.d/functions umask value(s) match the var_umask_for_daemons requirement">
df3ea4
     <ind:object object_ref="obj_umask_for_daemons" />
df3ea4
@@ -77,6 +71,8 @@
df3ea4
     <ind:var_ref>var_etc_init_d_functions_umask_as_number</ind:var_ref>
df3ea4
   </ind:variable_object>
df3ea4
 
df3ea4
+  
df3ea4
+       the referenced 'var_umask_for_daemons_as_number' OVAL definition -->
df3ea4
   <ind:variable_state id="ste_umask_for_daemons" version="1">
df3ea4
     <ind:value datatype="int" operation="bitwise and" var_ref="var_umask_for_daemons_umask_as_number" />
df3ea4
   </ind:variable_state>