All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SELinux <SELinux@tycho.nsa.gov>,
	"Fedora SELinux support list for users & developers."
	<fedora-selinux-list@redhat.com>
Subject: Re: Security contexts for the contexts directory?
Date: Thu, 27 May 2004 09:54:44 -0400	[thread overview]
Message-ID: <40B5F324.9010208@redhat.com> (raw)
In-Reply-To: <1085663772.1072.149.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:

>On Thu, 2004-05-27 at 07:54, Daniel J Walsh wrote:
>  
>
>>With the new design of the policy tree, we have moved the "contexts" 
>>files into
>>/etc/selinux/*/contexts/
>>
>>These files include default_contexts, file_contexts, default_type, 
>>failsafe_contexts ...
>>as well as contexts for individual users like users/root.  Currently the 
>>security contexts for these files is etc_t.   Should we change them so 
>>something else? default_contexts_t?  Should file_contexts be marked 
>>differently then the others?
>>    
>>
>
>I'd suggest a single type (other than etc_t) for default_contexts,
>default_type, failsafe_context, and the other files installed from
>policy/appconfig.  file_contexts should likely have a different type to
>allow different access, so perhaps it should have its own directory and
>type.  With the old layout and policy, it ends up in policy_config_t,
>but I think we want to distinguish it from the binary policy file as
>well as from the appconfig files.
>
>  
>
Ok how about, default_contexts_t for contexts directory and users 
directory.  Create a new directory called files and put file_contexts in 
there with a context of file_contexts_t.

>>Also since policy is determined by /etc/sysconfig/selinux, should we set 
>>a special security context on it?  If we do should we move it to a 
>>directory where it would be easier to maintain the security context?  
>>Maybe rename it to /etc/selinux/config?
>>    
>>
>
>I would prefer having a distinct type on it (and moving it to a
>directory with that type so that we can easily preserve the type), as
>the integrity of that file is critical to SELinux, at least in the
>Fedora Core implementation.
>
>  
>
Should that have default_contexts_t also? Or something different?

--
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.

  reply	other threads:[~2004-05-27 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 11:54 Security contexts for the contexts directory? Daniel J Walsh
2004-05-27 13:16 ` Stephen Smalley
2004-05-27 13:54   ` Daniel J Walsh [this message]
2004-05-27 14:27     ` Stephen Smalley

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=40B5F324.9010208@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=fedora-selinux-list@redhat.com \
    --cc=sds@epoch.ncsc.mil \
    /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.