Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When running an oscap report (after having either run with --remediate flag or manually addressing the issues), the report still marks a compliant value as failed.
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.40-12
How reproducible:
100%
Steps to Reproduce:
1. Run oscap utility with remediate flag
2. Verify contents of file
3. Run oscap utility in reporting-only mode
Actual results:
When Ciphers and MACs lines are as follows:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
MACs hmac-sha2-512,hmac-sha2-256
oscap utility reports the check items as failed
Expected results:
When Ciphers and MACs lines are as follows:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
MACs hmac-sha2-512,hmac-sha2-256
oscap utility should report the check items as passed
Additional info:
This issue was supposedly fixed upstream (with a reference to BZ 1413494) via commit https://github.com/ComplianceAsCode/content/pull/1767/commits/7bb9127f62df9154b5b7638fa8d4c8f714431f29, however, it still appears to be failing in current RHEL7.6 release/packaging
Just ran scan with manually adding the following to /etc/ssh/sshd_config off of a fresh 7.6 install:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
MACs hmac-sha2-512,hmac-sha2-256
The scan proceeds to pass with the above ^ configuration.
Can you please provide the contents of /etc/ssh/sshd_config, /etc/*release*, and a sosreport?
You can use soscleaner which is in EPEL or upstream from https://github.com/jduncan-rva/soscleaner
to obfuscate sensitive data if needed.