Red Hat Bugzilla – Bug 1302230
Hide default OSCAP profile
Last modified: 2017-08-01 16:33:23 EDT
Description of problem: Questions) When selecting in SCAP Content - XCCDF - "Default XCCDF profile", the result is not selected, when we change to another option, like PCI, the result works fine. Explanation) This is expected behavior. The default profile may contain rules. However stock policies (from scap-security-guide package) never have meaningful content. Satellite presents default profile as an option for customers that create their own policies, that can bring meaningful default profile. We can improve UX and hide default profile if that option is not meaningful given the content file. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: No meaningful oscap default profile. Expected results: Should have a meaningful default profile. Additional info:
This should be fixed in Proxy::OpenSCAP::ContentParser.extract_policies. At that point we can tell, whether the 'default' profile is useful or not. We should perhaps implement that function (to query usefulness) in rubygem-openscap.
Moving 6.2 bugs out to sat-backlog.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.