Bug 1803116
Summary: | oscap-ssh fails to retrieve the result files when --sudo is used | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
Component: | openscap | Assignee: | Jan Černý <jcerny> |
Status: | CLOSED ERRATA | QA Contact: | Matus Marhefka <mmarhefk> |
Severity: | medium | Docs Contact: | Jan Fiala <jafiala> |
Priority: | medium | ||
Version: | 8.1 | CC: | jafiala, jcerny, lmanasko, mhaicman, mmarhefk |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openscap-1.3.2-7.el8 | Doc Type: | Bug Fix |
Doc Text: |
.The `oscap-ssh` utility now works correctly when scanning a remote system with --sudo
When performing a Security Content Automation Protocol (SCAP) scan of a remote system using the `oscap-ssh` tool with the `--sudo` option, the `oscap` tool on the remote system saves scan result files and report files into a temporary directory as the `root` user. Previously, if the `umask` settings on the remote machine were changed, `oscap-ssh` might have been prevented access to these files. This update fixes the issue, and as a result, `oscap` saves the files as the target user, and `oscap-ssh` accesses the files normally.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 02:29:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Renaud Métrich
2020-02-14 14:14:11 UTC
Fixed upstream in https://github.com/OpenSCAP/openscap/pull/1485/files Thanks Matus. I checked the doc text and now it looks good to me. 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 (openscap 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-2020:4623 |