Bug 1499760
Summary: | gvfs-udisks2-volume-monitor generates huge amount of audit log with access denied messages | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Dmitry Zhukovski <dzhukous> | |
Component: | util-linux | Assignee: | Karel Zak <kzak> | |
Status: | CLOSED ERRATA | QA Contact: | Radka Brychtova <rskvaril> | |
Severity: | medium | Docs Contact: | ||
Priority: | urgent | |||
Version: | 7.4 | CC: | bxue, dzhukous, fkrska, fsumsal, jherrman, rskvaril, xzhou, zlang | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | util-linux-2.23.2-48.el7 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, using the "gvfs-udisks2-volume-monitor" command in some cases generated a large amount of audit logs with "access denied" error messages. With this update, the checks for write access to the private library files that the libmount library performs have been adjusted to prevent the error messages from appearing.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1506533 (view as bug list) | Environment: | ||
Last Closed: | 2018-04-10 17:27:15 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1506533 |
Description
Dmitry Zhukovski
2017-10-09 10:55:44 UTC
Yes, open() is probably overkill to test write access to the utab file. It seems eaccess() would be better. Radka - you have to have SElinux enabled and then boot desktop and try to search and mount some samba share for example. you should get tons of those messages. Re testing. Yes - customer successfully tested both 7.5 and 7.4.z fix and has got approved interim hotfix for 7.4.z *** Bug 1510976 has been marked as a duplicate of this bug. *** 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:0936 |