Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1566588 - textfilecontent* probes do not work in offline mode [rhel-7.5.z]
textfilecontent* probes do not work in offline mode [rhel-7.5.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openscap (Show other bugs)
7.5
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Matus Marhefka
Marek Haicman
Mirek Jahoda
: ZStream
Depends On: 1547107
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-12 10:59 EDT by Oneata Mircea Teodor
Modified: 2018-05-14 12:13 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the textfilecontent54 probe did not work properly in offline mode. As a consequence, the oscap-docker tool and the atomic scan command reported different results for the same rule that checked the contents of a file. With this update, the previous removal of the chroot() function in offline mode of the textfilecontent54 probe has been reverted. As a result, oscap-docker and atomic scan no longer report different results with the same rule in the described scenario.
Story Points: ---
Clone Of: 1547107
Environment:
Last Closed: 2018-05-14 12:13:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1405 None None None 2018-05-14 12:13 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-04-12 10:59:13 EDT
This bug has been copied from bug #1547107 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 7 errata-xmlrpc 2018-05-14 12:13:18 EDT
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, 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-2018:1405

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