Bug 1136569
Summary: | SELinux is preventing /usr/sbin/sstpc from 'setattr' accesses on the sock_file . | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andreas Lindhé <Lindhe94> |
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, gregoire, lvrabec, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:556632225d75022ead89686c1764ff8ca897df2324d5835d9e8f6bae1d9a9623 | ||
Fixed In Version: | selinux-policy-3.12.1-183.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-09 22:24:34 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
Andreas Lindhé
2014-09-02 22:16:28 UTC
0bf5dfe302c69a538e9d101dcd22970b3564a602 fixes this in git. *** Bug 1136574 has been marked as a duplicate of this bug. *** *** Bug 1136566 has been marked as a duplicate of this bug. *** commit 0bf5dfe302c69a538e9d101dcd22970b3564a602 Author: Dan Walsh <dwalsh> Date: Wed Sep 3 05:54:11 2014 -0400 Allow pppd to create sock_files in /var/run https://github.com/selinux-policy/selinux-policy/commit/ab2143ce194be8787996b1d705995b04b649ad82 selinux-policy-3.12.1-183.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-183.fc20 selinux-policy-3.12.1-183.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. Hum, I might have misreported this: I am on fedora 23, not 20 :-/ Did you recently get this problem? What AVC are you seeing? Sorry wrong thread, my problem is described in bug 1302666. :-/ |