Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix missing OVAL in some of RHEL 8 rules #4927

Merged
merged 4 commits into from
Oct 16, 2019

Conversation

jan-cerny
Copy link
Collaborator

Description:

Some of the rules in RHEL 8 becnhmark which aren't part of any RHEL 8 profile don't contain OVALs. This usually happens when OVAL hasn't been written yet. That's fine, but sometimes it's because of wrong prodtype elements or platform elements in OVAL or their mismatch. In this PR we don't add new OVALs but we try to address the second problem for some of the rules.

Read commit messages of each commit for specific details.

Rationale:

Users can add the rules to their profiles by tailoring, but if the rule is missing OVAL it has limited usability for them.

These rules have no OVAL in RHEL 8 benchmark.
pam_cracklib rules should be RHEL 6 only because since RHEL 7 the
pam_cracklib PAM module is replaced by pam_pwquality module.
This rule is used in OCP4, RHEL7, OL7, RHV4, WRLinux 10.19 and WRLinux 8
profiles. However, the OVAL was available only for RHEL 7 and WRLinux 8
which is not aligned with empty element in rule.yml. Since the rule
makes sense on most of the operating systems, we can mark the OVAL as
multi_platform_all.

The rhel7.xml and wrlinux.xml were almost identical, except the platform
element, so we can merge them in a single shared.xml.
This OVAL was marked as applicable only on RHEL 8,
but the OVAL could be enabled for RHEL8 as well.
Rule mount_option_krb_sec_remote_filesystems specifies prodtype
as wrlinux1019,rhel7,rhel8 but the OVAL was available only for
RHEL 7. It seems that we can use this OVAL on RHEL 8 and
WRLinux 10.19 as well.
@jan-cerny jan-cerny added this to the 0.1.47 milestone Oct 15, 2019
@matusmarhefka matusmarhefka self-assigned this Oct 16, 2019
@matusmarhefka
Copy link
Member

LGTM.

@matusmarhefka matusmarhefka merged commit 8ec6c63 into ComplianceAsCode:master Oct 16, 2019
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants