Bug 1404398

Summary:	variable ssg-var_etc_init_d_functions_umask_as_number is decimal, and it confuses users
Product:	Red Hat Enterprise Linux 7	Reporter:	Marek Haicman <mhaicman>
Component:	scap-security-guide	Assignee:	Watson Yuuma Sato <wsato>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	mgrepl, mhaicman, openscap-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-12 16:15:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marek Haicman 2016-12-13 18:21:37 UTC

Description of problem:
Variable ssg-var_etc_init_d_functions_umask_as_number is storing umask in decimal form, so it can be numerically compared to the umask in the guide. Unfortunately this value is shown in the report, and it's confusing to the user [as user expects 022 and not 18].

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.30-3.el7.noarch

How reproducible:
reliably

Steps to Reproduce:
1. perform scan with rule xccdf_org.ssgproject.content_group_daemon_umask
2. see results
3. Show all result details

Actual results:
Value of umask on the machine is printed in decimal 

Expected results:
Umask is printed in octal

Additional info:
String comparison instead?

Comment 2 Marek Haicman 2019-03-12 16:15:51 UTC

This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.