On 4/26/06, Richard Hally <rhallyx@xxxxxxxxxxxxxx> wrote:
When I updated to the latest targeted policy (see below), the configuration was changed to disabled! This is the second update that has made this change. The previous policy update was the first time that has happened and was reported by both myself and Tom London. Apparently the change listed in the 04/26 rawhide report (also below) needs further attention. installed on an updated rawhide system: selinux-policy-2.2.35-2 selinux-policy-targeted-2.2.35-2 libselinux-devel-1.30.3-1 libselinux-python-1.30.3-1 selinux-doc-1.25.2-1 selinux-policy-mls-2.2.35-2 libselinux-1.30.3-1 selinux-policy-strict-2.2.35-2 selinux-policy-2.2.35-2 ----------------------- * Tue Apr 25 2006 James Antill <jantill@xxxxxxxxxx> 2.2.35-2 - Add xm policy - Fix policygentool * Mon Apr 24 2006 Dan Walsh <dwalsh@xxxxxxxxxx> 2.2.35-1 - Update to upstream - Fix postun to only disable selinux on full removal of the packages <-------
I can verify this. I separately updated to today's 'selinux-policy*' packages, and check /etc/selinux/config before and afterwards. Before: SELINUX=enforcing Afterwards SELINUX=disabled tom -- Tom London -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
