On Wed, 2009-07-15 at 11:25 -0400, Hasan Rezaul-CHR010 wrote: > Hi All, > > I work on a product that uses Linux Kernel 2.6.21. We are > currently using the following SELinux libs and related package > versions: > > checkpolicy 1.33.1 > libselinux 2.0.13 > libsemanage 2.0.1 > libsepol 2.0.3 > libsetrans 0.1.18 > policycoreutils 2.0.16 > > I am implementing the "Strict" policy. And so I see the directory > structure on my machine as: > > ------------------------------------------- > /etc/selinux/config > /etc/selinux/restorecond.conf > /etc/selinux/semanage.conf > > /etc/selinux/strict/ > /etc/selinux/strict/contexts/ > /etc/selinux/strict/modules/ > /etc/selinux/strict/policy/ > /etc/selinux/strict/setrans.conf > /etc/selinux/strict/seusers > > -------------------------------------------- > > > We are moving to a newer Linux version 2.6.27 (that's packaged for us by > a third-party company), and as a result of this newer OS delivery, we > will automatically get moved to the SELinux package version: > > checkpolicy svn2950 > libselinux svn2950 > libsemanage svn2950 > libsepol svn2950 > libsetrans N/A > policycoreutils svn2950 > > > ** My questions are: > > 1. I see the /etc/selinux/ directory structure is quite different for > the svn2950 version! Is it supposed to be that way ? > > 2. Is the difference in directory structure due to the svn2950 package > version, or is it because of a newer Linux kernel version ? (Linux > 2.6.21 vs. Linux 2.6.27) > > 3. Is the 'strict' policy supported in this svn2950 version? > > 4. In the LATEST officially released version(s) of the Selinux packages > from http://userspace.selinuxproject.org/trac/wiki/Releases, is the > /etc/selinux/ directory structure the same as I have described in the > --- block --- above, or did it change ? > > 5. Does the LATEST officially supported versions still support "strict" > policy, or does it only support "targeted" ?? It supports "strict policy" but the strict policy model merged with the targeted policy model. You would have to configure the Targeted SELinux policy to make it strict. > > 6. Has the concept of "targeted" policy changed since about two years > ago ? Not really. Targeted policy still targets a set of processes and the rest goes into the unconfined domain. However, now it is possible to uninstall the unconfined module which effectively turns your targeted policy into a strict policy. Basically the targeted policy was extended by the merger with strict policy. > Thanks in advance for all your help. > > > -- > This message was distributed to subscribers of the selinux mailing list. > If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with > the words "unsubscribe selinux" without quotes as the message.
Attachment:
signature.asc
Description: This is a digitally signed message part
