RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Ansible remediations for mount_option_dev_shm_noexec and openssl_use_strong_entropy are not aligned with their counterpart OVAL checks. Scan after applying these Ansible remediations produce fail result while scan after Bash remediations produces pass.

For the rule openssl_use_strong_entropy the reason is that Ansible remediation is not including a newline at the end of the produced /etc/profile.d/openssl-rand.sh file which makes its sha256 different than expected by OVAL.


Version-Release number of selected component (if applicable):
scap-security-guide-0.1.49-1.el8.noarch


How reproducible:
always


Steps to Reproduce:
1. Run Ansible remediations for mount_option_dev_shm_noexec and openssl_use_strong_entropy rules.
2. Scan after applying the Ansible remediations.


Actual results:
The mount_option_dev_shm_noexec and openssl_use_strong_entropy rules are not fixed by Ansible remediations with respect to their OVAL checks.

Expected results:
The mount_option_dev_shm_noexec and openssl_use_strong_entropy rules are fixed by Ansible remediations with respect to their OVAL checks.

The issue with mount_option_dev_shm_noexec should be fixed by:
- https://github.com/ComplianceAsCode/content/pull/5765
- https://github.com/ComplianceAsCode/content/pull/5752

The issue with openssl_use_strong_entropy should be fixed by:
- https://github.com/ComplianceAsCode/content/pull/5577

Swithching to Modified, as the patch is part of the 0.1.50 version, which is the current one after the May rebase.

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 (scap-security-guide bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:4626