Bug 808952
Summary: | SELinux is preventing /usr/lib/systemd/systemd-multi-seat-x from 'write' accesses on the directory systemd. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | shawnlandden |
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: | 17 | CC: | dominick.grift, dwalsh, jerome, lpoetter, mgrepl, systemd-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | abrt_hash:8848ed33c64e232985a1289b97349ccb107f665442f40522e3d6e37710414b14 | ||
Fixed In Version: | selinux-policy-3.10.0-116.fc17 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-18 23:07:32 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
shawnlandden
2012-04-02 00:40:08 UTC
Any idea what directory/file it is trying to write? Is this writing content into /run/systemd /run/systemd/multi-session-x/ /run/systemd/multi-session-x /run/plymouth/pid Systemd guys what processess have to be able to write here? Read Hear? Currently we have /var/run/systemd/seats(/.*)? gen_context(system_u:object_r:systemd_logind_var_run_t,s0) /var/run/systemd/sessions(/.*)? gen_context(system_u:object_r:systemd_logind_sessions_t,s0) /var/run/systemd/users(/.*)? gen_context(system_u:object_r:systemd_logind_var_run_t,s0) Should we label multi-session-x the same? Should we treat systemd-multi-seat-x like we treat /lib/systemd/systemd-logind > Any idea what directory/file it is trying to write? Is this writing content into /run/systemd yes http://cgit.freedesktop.org/systemd/systemd/tree/src/login/multi-seat-x.c#n115 > Should we label multi-session-x the same? Should we treat
> systemd-multi-seat-x
> like we treat /lib/systemd/systemd-logind
multi-seat-x is its own executable, and is an ugly wrapper around X until X gains this functionality natively
I dont think it needs access to the rules you listed above. The X server does need read access to the xorg.conf this wrapper writes out
Ok I am going to label this as xdm_var_run_t. /var/run/systemd/multi-session-x(/.*)? gen_context(system_u:object_r:xdm_var_ru And allow xdm_t to create it. Does anything in systemd need to manage this directory? multi-seat-x writes a throw-away configuration file for X to add graphics multi-seat support to X until X learns this natively. > And allow xdm_t to create it. Does anything in systemd need to manage this
directory?
no
Fixed in selinux-policy-3.10.0-114.fc17 selinux-policy-3.10.0-116.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-116.fc17 selinux-policy-3.10.0-116.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |