Bug 1142551
Summary: | SELinux is preventing /usr/bin/du from 'read' accesses on the directory . | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kristjan Stefansson <hk.stefansson> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | dominick.grift, dwalsh, lvrabec, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:6567efaf6b6c39079512606665dab257db0192f6a015c40eca105d423c91bf8a | ||
Fixed In Version: | selinux-policy-3.12.1-189.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-16 02:00:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kristjan Stefansson
2014-09-17 03:38:04 UTC
commit e94442c35c860b1651597de5ed22e4764c5fa092 Author: Miroslav Grepl <mgrepl> Date: Wed Sep 17 12:15:11 2014 +0200 Allow du running in logwatch_t read hwdata. selinux-policy-3.12.1-189.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-189.fc20 Package selinux-policy-3.12.1-189.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-189.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12350/selinux-policy-3.12.1-189.fc20 then log in and leave karma (feedback). selinux-policy-3.12.1-189.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |