Bug 1238080

Summary: Better text for default profile
Product: Red Hat Enterprise Linux 7 Reporter: Šimon Lukašík <slukasik>
Component: oscap-anaconda-addonAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jikortus
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: oscap-anaconda-addon-0.7-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:31:58 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1186677    

Description Šimon Lukašík 2015-07-01 07:27:45 UTC
Oscap-Anaconda-Addon allows user to choose security policy to be applied (XCCDF Profile). The content may define multiple profiles. However the XCCDF Standard defines something named 'default profile', which is always there. Anaconda uses following texts to describe this default profile to the user:

    Default
    The default profile.

That looks sane to uneducated (unaware of inner workings of XCCDF) user. The chances are that such user will proceed with this 'default' option.

However, well formed XCCDF content will be written in a way that makes default profile 'no-op'. That is however not clear to the uneducated mass.

Please consider using following texts for the default profile:

    Default
    The implicit XCCDF profile. Usually, the default contains no rules.



Actual results:
    The default profile.

Expected results:
    The implicit XCCDF profile. Usually, the default contains no rules.
    (or similar text).

Comment 3 errata-xmlrpc 2015-11-19 11:31:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2330.html