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 1722003 - OpenSCAP probes produce obtrusive data
Summary: OpenSCAP probes produce obtrusive data
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openscap
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 8.2
Assignee: Jan Černý
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-19 11:05 UTC by Jan Černý
Modified: 2024-12-20 18:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-01 07:41:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
OVAL definitions (3.03 KB, application/xml)
2019-06-19 11:05 UTC, Jan Černý
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1970529 1 low CLOSED oscap complains about missing resources even though they were downloaded locally 2024-12-20 20:17:24 UTC

Description Jan Černý 2019-06-19 11:05:43 UTC
Created attachment 1582171 [details]
OVAL definitions

Description of problem:
When evaluating attached OVAL definitions that uses OVAL sets OpenSCAP prints warnings about obtrusive data.

Version-Release number of selected component (if applicable):
openscap-1.3.0-7.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. oscap oval eval oval.xml


Actual results:
W: oscap:     Obtrusive data from probe!
W: oscap:     Obtrusive data from probe!
Definition oval:test-sssd:def:1: false
Evaluation done.


Expected results:
No warnings.

Additional info:
Check if OVAL results are expected.

Comment 2 Jan Černý 2020-09-25 13:44:14 UTC
This link shows that we should investigate it further: https://github.com/OpenSCAP/openscap/pull/1502

Comment 4 Jan Černý 2020-12-14 14:58:25 UTC
We need to fix this. The previous attemp to fix wasn't successful. Now, it started to be a potential problem for SCAP certification as this warning is produced with validation test content. See https://github.com/OpenSCAP/openscap/issues/1632. Definitely it will be embarrassing.

Comment 6 Jan Černý 2021-01-28 09:41:04 UTC
https://github.com/OpenSCAP/openscap/pull/1678

Comment 7 Jan Černý 2021-01-29 08:30:11 UTC
and also additional PR https://github.com/OpenSCAP/openscap/pull/1679

Comment 9 RHEL Program Management 2021-02-01 07:41:36 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.