Description of problem: Start a user session in KDE using the KDM. Since a user session nees to be able to create (and read, write, and delete) the sesson errors file. this is a likely oversight in the latest targeted file, eh? 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.1-2.fc20.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-24.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.9.0-0.rc4.git0.1.fc19.x86_64 #1 SMP Mon Mar 25 02:31:02 UTC 2013 x86_64 x86_64 Alert Count 7 First Seen 2013-03-26 15:52:16 PDT Last Seen 2013-03-29 10:25:26 PDT Local ID fb826867-f552-430a-b1aa-e1bbc1879107 Raw Audit Messages type=AVC msg=audit(1364577926.921:455): avc: denied { create } for pid=2153 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(1364577926.921:455): arch=x86_64 syscall=open success=no exit=EACCES a0=e3c260 a1=4c1 a2=180 a3=0 items=0 ppid=2103 pid=2153 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 ============== mta_mailserver_delivery(xdm_t) Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport Potential duplicate: bug 922155
Fixed in selinux-policy-3.12.1-25.fc19.noarch
Description of problem: AVC shows up just on install and reboot to installed system with F19 Alpha TC5 KDE live, no user interaction needed. Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 type: libreport
selinux-policy-3.12.1-28.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2013-5045/selinux-policy-3.12.1-28.fc19
Package selinux-policy-3.12.1-28.fc19: * should fix your issue, * was pushed to the Fedora 19 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-28.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5045/selinux-policy-3.12.1-28.fc19 then log in and leave karma (feedback).
Proposing as a final release blocker: "In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) ". Also AlphaFreezeException, kind of as a proxy - I think it would be good to get the latest selinux-policy into Alpha now we slipped, it fixes an awful lot of restrictions and doesn't tighten anything down, so it should be safe and reduce the number of AVCs we see in install and post-install testing.
+1 to getting in Alpha
+1 for AlphaFreezeException
That's +3, setting Accepted.
selinux-policy-3.12.1-28.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
I am getting this denial with selinux-policy-targeted-3.12.1-74.9.fc19.noarch when I log in remotely (with VNC) to a MATE session. I am using KDM with XDMCP. Here are the detailed audit messages: type=SYSCALL msg=audit(1382105196.159:1328): arch=c000003e syscall=2 success=no exit=-13 a0=7f7e27496990 a1=4c1 a2=180 a3=ffffffe0 items=0 ppid=31738 pid=31756 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=106 tty=(none) comm="kdm" exe="/usr/bin/kdm" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1382105196.159:1328): avc: denied { create } for pid=31756 comm="kdm" name=".xsession-errors-localhost:10" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:user_home_t:s0 tclass=file
Do you have the xdm_write_home boolean turned on? # setsebool -P xdm_write_home 1 If it exists in F19...
(In reply to Daniel Walsh from comment #11) > Do you have the xdm_write_home boolean turned on? > > # setsebool -P xdm_write_home 1 > > If it exists in F19... It does exist in F19, and it wasn't turned on. Not sure why I didn't think to look for a relevant boolean. I just double-checked, and SETroubleshoot didn't mention that boolean in its output. Should I file a bug against setroubleshoot-plugins?
Might have been a boolean we created in Fedora 20
Yes, it was created just in F20. Lukas, could you back port it.
(In reply to Miroslav Grepl from comment #14) > Yes, it was created just in F20. > > Lukas, > could you back port it. Just to make sure everyone is on the same page, the boolean is definitely present on my F19 system: [pilcher@ian ~]$ getsebool xdm_write_home xdm_write_home --> off [pilcher@ian ~]$ cat /etc/fedora-release Fedora release 19 (Schrödinger’s Cat) [pilcher@ian ~]$ rpm -q selinux-policy-targeted selinux-policy-targeted-3.12.1-74.10.fc19.noarch Are you talking about enhancing SETroubleshoot to tell people about this boolean when the relevant AVC occurs?
OK, You are right. The boolean has been back ported.