Bug 542017
| Summary: | SELinux is preventing /usr/bin/xauth "read" access on /proc/<pid>/status. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mitchell Richters <mjr4077au> |
| Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | dwalsh, kybernetikkollektiv, mgrepl, Triv |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:14bf9bd35529e5383734fe39815416fa18f0289c6de389ed9d4f071ed3f8a50d | ||
| Fixed In Version: | 3.6.32-55.fc12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-07 22:47:07 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
Mitchell Richters
2009-11-27 23:37:34 UTC
Nvidia devices seem to be getting created with the wrong label. Does xauth seem to be working correctly? > Does xauth seem to be working correctly?
How can one test this?
Do your X apps seem to be working correctly when you login? WHen you launch apps as root? If you ssh -X -Y into a box? I would figure it is working fine. When I login as normal user everything is working fine. But there are indeed some problems when I try to launch apps as root, although I'm unsure if this isn't a topic of its own: In KDE, when I type 'kdesu dolphin' SELinux comes up with a security alert; basically it says: SELinux is preventing /bin/bash "write" access to /var/lib/misc/prelink.quick. [xauth has a permissive type (xauth_t). This access was not denied.] SELinux denied access requested by xauth. It is not expected that this access is required by xauth and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. This alert has occurred 33 times since Mon Nov 30, 2009 at 04:07:48 PM CET After this dolphin starts but is not fully functional: One can browse directories etc but it one tries to, for example, open a text file, a KDE message dialog box pops up saying "KDEInit could not launch '/usr/bin/kwrite'.". Right now I don't have the ability to try remote login into this machine, but I will check this tomorrow. *** Bug 543479 has been marked as a duplicate of this bug. *** I have some fixes for the labels. Fixed in selinux-policy-3.6.32-53.fc12.noarch Remote login and execution of X/KDE applications works fine without any errors or warnings. selinux-policy-3.6.32-55.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/selinux-policy-3.6.32-55.fc12 selinux-policy-3.6.32-55.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12650 selinux-policy-3.6.32-55.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |