Description of change/FAQ addition. If a change, include the original
text first, then the changed text:
Here is a question that may be worthwhile to have in the FAQ:
Q: I have installed Fedora Core 2 without SELinux, what are the steps
to start using SELinux?
1. Install the policy<version>.rpm ,
(list other needed packages here.)
2. change the /etc/sysconfig/selinux file to have SELINUX=permissive
(if you had selinux=0 on the kernel line in grub, take it off)
(so that the LSM and SELinux modules will be loaded).
4. cd /etc/security/selinux/src/policy
(to make sure the policy and file_contexts were built correctly)
(this will take a while, it accesses every file on the system)
(2nd time, to restart all programs with the correct contexts)
This needs to be checked.
If this is not correct, please give the correct steps.
Version-Release of FAQ (found on
for example selinux-faq-1.1 (2004-05-05-T16:20-0800)
I wonder if there is a configuration problem with the policy files.
In the /etc/security/selinux/src/policy/Makefile (mine at least),
there is no mention of policy.17 as an output file, but I do have a
policy.17 file in that directory and in the /etc/security/selinux
directories (see below).
Where are all of these things dropping from, and what is the source
used in generating policy.15, policy.16, policy.17.
Also, what is the meaning of 'load' when applied to a policy file. And
how can one determine what policy file is 'active'?
[root@hoho2 policy]# more /home/user1/policy.bug
[root@hoho2 policy]# pwd
[root@hoho2 policy]# grep 15 Makefile
$(CHECKPOLICY) -c 15 -o $(INSTALLDIR)/policy.15 policy.conf
[root@hoho2 policy]# grep 16 Makefile
$(CHECKPOLICY) -c 16 -o $(INSTALLDIR)/policy.16 policy.conf
[root@hoho2 policy]# grep 17 Makefile
[root@hoho2 policy]# ls -l ../..
-rw-r--r-- 1 root root 86912 May 5 23:30 file_contexts
-rw-r--r-- 1 root root 7369029 May 5 23:30 policy.15
-rw-r--r-- 1 root root 7370766 May 5 23:30 policy.16
-rw-r--r-- 1 root root 7371078 May 5 23:29 policy.17
drwx------ 3 root root 4096 Apr 28 21:04 src
[root@hoho2 policy]# ls -l ../../policy.17
-rw-r--r-- 1 root root 7371078 May 5 23:29 ../../policy.17
[root@hoho2 policy]# ls -l policy.17
-rw------- 1 root root 7346892 Apr 28 21:04 policy.17
These are not the same files, both size and date differ.
[root@hoho2 policy]# file policy.17
policy.17: SE Linux policy v17 6 symbols 7 ocons
That is pretty nifty. Maybe having some sort of 'source stamp' would
be a useful addition somewhere, not necessarily in the file text
though. (But maybe)
[root@hoho2 policy]# checkpolicy -h
checkpolicy: invalid option -- h
usage: checkpolicy [-b] [-d] [-c policyvers (15-17)] [-o
[root@hoho2 policy]# checkpolicy -b policy.17
checkpolicy: loading policy configuration from policy.17
security: 5 users, 7 roles, 1244 types, 1 bools
security: 30 classes, 301755 rules
checkpolicy: policy configuration loaded
Loaded? What does that mean? Have I accidently changed my whole
No indication of what policy.conf or other files were used to make up
this (binary) file.
Moving second comment to it's own bug, bz122849; adding back blocking
Update - as soon as I grab final FC2 ISOs, I'm going to make this one
of my installation tests, which will give me a chance to test these
steps from scratch. I'll likely generate a package needs list from
the diff between the two installs (w/ and w/o SELinux).
*** Bug 125148 has been marked as a duplicate of this bug. ***
The below steps were added to the FC2 version of the SELinux FAQ,
currently archived at:
## begin FAQ entry
Q:. How do I install SELinux on a running Fedora Core 2 that didn't
have SELinux installed through Anaconda?
A:. Since SELinux is now part of the kernel, installation is
straightforward. You are enabling systems already in place.
1. Install a policy with yum install policy policy-sources.
2. Create or edit /etc/sysconfig/selinux and set SELINUX=permissive
3. Relabel your file system with fixfiles relabel. This will take
at least several minutes, as each file on the system is checked and
labeled for the newly installed policy.
4. Reboot your system. Check /var/log/messages for avc: denied
messages. Resolve any issues while still in permissive mode, and once
you can boot without avc denials, set SELINUX=enforcing in