Tom London wrote:
I updated to selinux-policy-strict-1.13.9-1 off of the development tree, andI'm not having the same problem, having just finished doing a "yum update" from the /development tree(including the above policy). The procedure I followed (because of the new policy) was immediately reboot with "a" selected at the grub menu and adding 'single' to the kernel line. doing fixfile relabel(delete /tmp? y) and then doing "reboot" at the prompt. the system comes up in enforcing mode to runlevel 5, I can do the graphical loging and su -.
immediately had problems:
'su' no longer is accessible
graphical login/X no longer works.
I bugzilla'ed this (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126788)
and attached a copy of the AVCs produced when rebooting with 'enforcing=0'.
tom
-- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-selinux-list
There are many more avc denied messages in /var/log/messages than previously(many having to do with hotplug).
Perhaps trying the above approach to relabeling will at least get you logged in.
HTH
Richard Hally
