Created attachment 936227 [details] rpm -qa output Description of problem: can't log in when enforcing is on Version-Release number of selected component (if applicable): selinux-policy-3.13.1-78.fc21 How reproducible: Every time Steps to Reproduce: 1. Try to boot with enforcing on in mode 3 Actual results: Can't log in. Login prompt returns. Expected results: Login Additional info: If I boot in permissive mode, the line "audit: type=1305 audit(1410344878.926:3): audit_pid=730 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 res=1" appears in /var/log/messages. Attaching a list of packages on my live build. Looked at bug 1139751, but I think this one is different because I don't see a mention of dbus.
What does dmesg |grep avc if you boot in permissive?
Created attachment 936672 [details] AVC alert details window I booted in Permissive. dmesg | grep avc gave: "[ 161.698776] systemd-readahead[582]: /usr/lib64/libavc1394.so.0.3.0: page 0 to 4 " Set enforcing. Using CTRL-ALT-2, tried to login as liveuser. Returning to CTRL-ALT-1, found I had a selinux alert, details of which are in this attachment. $ rpm -qa | grep selinux gives: "selinux-policy-devel-3.13.1-79.fc21.noarch libselinux-2.3-4.fc21.x86_64 libselinux-python-2.3-4.fc21.x86_64 selinux-policy-targeted-3.13.1-80.fc21.noarch libselinux-utils-2.3-4.fc21.x86_64 rpm-plugin-selinux-4.12.0-0.rc1.2.fc21.x86_64 selinux-policy-mls-3.13.1-80.fc21.noarch selinux-policy-minimum-3.13.1-80.fc21.noarch selinux-policy-3.13.1-80.fc21.noarch libselinux-debuginfo-2.3-4.fc21.x86_64 " Does it matter that selinux-policy-devel is still the version on the mirrors? (I'll fix that in my next build cycle.) "rpm -qa | grep light" gives: "lightdm-gtk-1.8.5-4.fc21.x86_64 lightdm-1.10.1-5.fc21.x86_64 lightdm-gobject-1.10.1-5.fc21.x86_64 "
Created attachment 936699 [details] first .TE file 1. Booted in Permissive. 2. Found a selinux alert. 3. In response to its details, entered the first suggested command: "/sbin/restorecon -v /etc/X11/xinit/Xsession" 4. CTRL-ALT-2, logged in as liveusersetenforce 1 5. CTRL-ALT-1, found another SELINUX alert. 6. In response to its details, entered the first suggested command: "/sbin/restorecon -v /usr/bin/bash" 7. setenforce 1 8. CTRL-ALT-F2 9. liveuser login was rejected 10. CTRL-ALT-F1 11. From the first selinux alert window, entered "grep login /var/log/audit/audit.log | audit2allow -M mypol semodule -i mypol.pp" 12. I think I tried Steps 8, 9 and 10 again, getting another reject. 13. From the first selinux alert window, entered "grep lightdm /var/log/audit/audit.log | audit2allow -M mypol1 semodule -i mypol1.pp" 14. CTRL-ALT-F2 15. login works Conclusion: the solution to this bug is in the commands I entered, and/or the .te files I generated (attached). Careful review is needed to avoid unnecessary security risk exposure.
Created attachment 936700 [details] second .TE file
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.