Red Hat Bugzilla – Bug 707629
defined booleans which have no effect
Last modified: 2011-05-26 15:50:40 EDT
Description of problem:
Some booleans are defined in targeted policy but have no effect on a system running that policy.
1. assumption: "seinfo -b /etc/selinux/targeted/policy/policy.21" displays booleans which are defined in the binary policy file
2. assumption: "sesearch -C --all /etc/selinux/targeted/policy/policy.21 | grep user_ping" displays all rules associated with user_ping boolean
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# for I in mls strict targeted ; do echo $I ; seinfo -b /etc/selinux/$I/policy/policy.21 2>/dev/null | wc -l ; done
# seinfo -b /etc/selinux/targeted/policy/policy.21 2>/dev/null | grep user_ping
# sesearch -C --all /etc/selinux/targeted/policy/policy.21 | grep user_ping | wc -l
* user_ping boolean is defined in targeted policy, but enabling/disabling of the boolean has no effect on a system running targeted policy
* user_ping boolean is NOT defined in targeted policy, because enabling/disabling of the boolean would have no effect in a system running targeted policy
* other booleans which have no effect in targeted policy: user_direct_mouse, user_dmesg, user_net_control, user_rw_noexattrfile, user_tcp_server, user_ttyfile_stat
While true I don't think this is something we want to change, because it could effect strict and MLS policy for little benefit.
In RHEL6 these booleans have meaning.