Back to bug 2228472

Who When What Removed Added
Red Hat Bugzilla 2023-08-02 12:25:10 UTC Pool ID sst_security_compliance_rhel_8
Milan Lysonek 2023-08-02 13:21:24 UTC Doc Type If docs needed, set a value Bug Fix
Doc Text Cause:
the OVAL check of SCAP rule xccdf_org.ssgproject.content_rule_postfix_prevent_unrestricted_relay was too strict and it did not account for Postconf configuration assignment statements which contained white spaces around the "=" sign.

Consequence:
The rule was reported as failing in the final report eventhough there existed a configuration technically meeting requirements of the rule.

Fix:
The rule was modified so that the check accepts statements with white spaces around the "=" sign.

Result:
Rule is now marked as passing in the final report for correct configuration statements.
Red Hat One Jira (issues.redhat.com) 2023-08-02 13:22:03 UTC Link ID Red Hat Issue Tracker RHELPLAN-164175
Vojtech Polasek 2023-08-04 07:42:39 UTC Status NEW POST
AutoMiloš 2023-08-04 15:37:31 UTC Fixed In Version scap-security-guide-0.1.69-1.el8_6
Keywords AutoVerified
Matus Marhefka 2023-08-08 11:50:58 UTC Status POST MODIFIED
errata-xmlrpc 2023-08-10 10:00:54 UTC Status MODIFIED ON_QA
Milan Lysonek 2023-08-14 14:32:08 UTC QA Contact qe-baseos-security mlysonek
Doc Text Cause:
the OVAL check of SCAP rule xccdf_org.ssgproject.content_rule_postfix_prevent_unrestricted_relay was too strict and it did not account for Postconf configuration assignment statements which contained white spaces around the "=" sign.

Consequence:
The rule was reported as failing in the final report eventhough there existed a configuration technically meeting requirements of the rule.

Fix:
The rule was modified so that the check accepts statements with white spaces around the "=" sign.

Result:
Rule is now marked as passing in the final report for correct configuration statements.
Cause:
The OVAL check of SCAP rule postfix_prevent_unrestricted_relay was too strict and it did not account for Postconf configuration assignment statements which contained white spaces around the "=" sign.

Consequence:
The rule was reported as failing in the final report even though there existed a configuration technically meeting requirements of the rule.

Fix:
The rule was modified so that the check accepts statements with white spaces around the "=" sign.

Result:
Rule is now marked as passing in the final report for correct configuration statements.
Status ON_QA VERIFIED

Back to bug 2228472