Description of problem: When system-config-securitylevel is used to switch
SELinux from disabled to enabled the file /.autorelabel must be created.
Systems which were installed or run for any time with selinux disabled will have
files with incorrect or no SELinux context. This causes the system to work very
poorly if at all.
The existance of /.autorelabel is checked by rc.sysinit on bootup and relabels
all of the files on the FS with the best selinux labels it can. We cannot
reasonably expect users to use the gui to change from disabled to enabled and
then to go to the command line and run "touch /.autorelabel"
Moving from enabled to disabled does not need any modification. There also does
not need to be any changes when moving from enforcing to permissive or vice
versa. This file only needs to be created when changing from disabled to enabled.
Version-Release number of selected component (if applicable): Latest RHEL4 and FC4
How reproducible: Always
Steps to Reproduce:
1. run system-config-securitylevel
2. disable selinux
3. enables selinux
4. check for the existance of /.autorelabel
No file created
Empty /.autorelabel file created
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.