All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Hasan Rezaul-CHR010 <CHR010@motorola.com>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: /etc/selinux/  directory structure...
Date: Wed, 15 Jul 2009 12:01:17 -0400	[thread overview]
Message-ID: <4A5DFD4D.5030507@redhat.com> (raw)
In-Reply-To: <D06FE0A2807BC145B0D38744789D4F5D06F02EC0@de01exm68.ds.mot.com>

On 07/15/2009 11:25 AM, 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" ??
> 
> 6. Has the concept of "targeted" policy changed since about two years
> ago ?
> 
> Thanks in advance for all your help.


What is your security goals for using strict policy.  If it is confining the user, then you have this available in targeted policy.  If you do not want any unconfined domains to run on the system you can get this also, by removing the unconfined.pp and unconfineduser.pp modules.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  parent reply	other threads:[~2009-07-15 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D06FE0A2807BC145B0D38744789D4F5D06817A56@de01exm68.ds.mot.com>
     [not found] ` <13D6E9E0302C0E4B9EE667132D21766C02B8342F@ala-mail09.corp.ad.wrs.com>
2009-07-15 15:25   ` /etc/selinux/ directory structure Hasan Rezaul-CHR010
2009-07-15 15:57     ` Dominick Grift
2009-07-15 16:09       ` Hasan Rezaul-CHR010
2009-07-15 16:28         ` Dominick Grift
2009-07-15 16:01     ` Daniel J Walsh [this message]
2009-07-15 17:42 Hasan Rezaul-CHR010
2009-07-15 18:29 ` Dominick Grift

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5DFD4D.5030507@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=CHR010@motorola.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.