Description of problem: SELinux is preventing /usr/bin/kdm from 'create' accesses on the file .xsession-errors-:0. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that kdm should be allowed create access on the .xsession-errors-:0 file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep kdm /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:user_home_t:s0 Target Objects .xsession-errors-:0 [ file ] Source kdm Source Path /usr/bin/kdm Port <Unknown> Host (removed) Source RPM Packages kdm-4.10.0-10.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-20.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.8.0-2.fc19.x86_64 #1 SMP Wed Feb 20 00:35:44 UTC 2013 x86_64 x86_64 Alert Count 2 First Seen 2013-03-15 15:33:39 CET Last Seen 2013-03-15 15:34:54 CET Local ID 1ed32e19-34be-412f-a9d7-f5e9f09c2835 Raw Audit Messages type=AVC msg=audit(1363358094.671:365): avc: denied { create } for pid=1964 comm="kdm" name=".xsession-errors-:0" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:user_home_t:s0 tclass=file type=SYSCALL msg=audit(1363358094.671:365): arch=x86_64 syscall=open success=no exit=EACCES a0=f17060 a1=4c1 a2=180 a3=ffffff80 items=0 ppid=1931 pid=1964 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=2 tty=(none) comm=kdm exe=/usr/bin/kdm subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash: kdm,xdm_t,user_home_t,file,create audit2allow #============= xdm_t ============== allow xdm_t user_home_t:file create; audit2allow -R require { type xdm_t; } #============= xdm_t ============== userdom_manage_user_home_content_files(xdm_t) Additional info: hashmarkername: setroubleshoot kernel: 3.8.0-2.fc19.x86_64 type: libreport
Why is kdm creating this file in the users homedir rather then /run like gdm does? Is this new functionality? We currently have transition rules for .xsession-errors. sesearch -T -s xdm_t | grep .xsession-errors type_transition xdm_t admin_home_t : file xdm_home_t ".xsession-errors"; type_transition xdm_t user_home_dir_t : file xdm_home_t ".xsession-errors"; Is the goal here to support many Xsessions?
kdm has done it this way... for ever. I don't mind working to move things around, perhaps to match what gdm does (which seems to be a fun moving target from release to release)
Ok so maybe we tightened this up. I will add transition rules for a bunch of them.
Fixed in selinux-policy-3.12.1-22.fc19
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
selinux-policy-3.12.1-83.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-83.fc20
Package selinux-policy-3.12.1-83.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-83.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17722/selinux-policy-3.12.1-83.fc20 then log in and leave karma (feedback).
Package selinux-policy-3.12.1-84.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-84.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17722/selinux-policy-3.12.1-84.fc20 then log in and leave karma (feedback).
Description of problem: New install. Additional info: reporter: libreport-2.2.0 hashmarkername: setroubleshoot kernel: 3.13.6-200.fc20.x86_64 type: libreport
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.