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.
Bug 2013159 - rsyslog_encrypt_offload_* rules fail after ansible remediation
Summary: rsyslog_encrypt_offload_* rules fail after ansible remediation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Milan Lysonek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-12 09:18 UTC by Milan Lysonek
Modified: 2022-05-10 14:43 UTC (History)
3 users (show)

Fixed In Version: scap-security-guide-0.1.59-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 14:15:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-99490 0 None None None 2021-10-12 09:18:29 UTC
Red Hat Product Errata RHBA-2022:1900 0 None None None 2022-05-10 14:15:52 UTC

Description Milan Lysonek 2021-10-12 09:18:07 UTC 
Description of problem:
rsyslog_encrypt_offload_* ansible remediations set incorrect option to rsyslog configuration file.

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

How reproducible:
always

Steps to Reproduce:
1. ansible-playbook -t rsyslog_encrypt_offload_actionsendstreamdrivermode -i "localhost," /usr/share/scap-security-guide/ansible/rhel8-playbook-stig.yml
2. oscap xccdf eval --profile stig --rule xccdf_org.ssgproject.content_rule_rsyslog_encrypt_offload_actionsendstreamdrivermode /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml

Actual results:
Scan result is fail

Expected results:
Scan result is pass

Additional info:
Content project has 3 rsyslog_encrypt_offload_* rules:
- rsyslog_encrypt_offload_actionsendstreamdriverauthmode
- rsyslog_encrypt_offload_actionsendstreamdrivermode
- rsyslog_encrypt_offload_defaultnetstreamdriver

As an example, I will describe rsyslog_encrypt_offload_defaultnetstreamdriver rule:
The rsyslog option has $ prefix, in this case the option is $DefaultNetstreamDriver. But after application of ansible remediation the configuration file has this content:
\$DefaultNetstreamDriver gtls

The option is wrong in ansible playbook, the dollar sign should not be escaped.
Comment 1 Vojtech Polasek 2021-10-14 09:58:33 UTC 
Analysis:
The ansible playbook contains \$ where there should be only $. This occurs at the begining of configuration line.
This has been fixed upstream:
https://github.com/ComplianceAsCode/content/pull/7570
But I am not moving it into the POST state, as I think that the fix might be not ideal. It drops the backslash from the $ sign. But the line is used both as regex and as a line to be inserted. By dropping the backlash, the regex becames wrong. I will try to suggest a fix.
Comment 2 Watson Yuuma Sato 2021-12-01 13:27:52 UTC 
This patch follows up on Vojtech's concerns:
https://github.com/ComplianceAsCode/content/pull/7755
Comment 15 errata-xmlrpc 2022-05-10 14:15:29 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 (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-2022:1900
Note You need to log in before you can comment on or make changes to this bug.