All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: [Fwd: Unable to create files when using "context"option for	NFS]
Date: Wed, 08 Jun 2005 22:47:47 -0400	[thread overview]
Message-ID: <42A7ADD3.7060603@redhat.com> (raw)
In-Reply-To: <1118243446.26902.137.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:

>On Wed, 2005-06-08 at 10:48 -0400, Daniel J Walsh wrote:
>  
>
>>What is the best way to handle this? 
>>
>>If I add a rule
>>
>>allow file_type self:filesystem associate;
>>
>>Will that cause and explosion in rules?  Will this open a security risk?
>>
>>We tell people to use the mount -o context flags but policy can not 
>>handle most of them without the above rule. 
>>    
>>
>
>If possible, it would be preferable to enumerate the specific cases
>where we want to allow such associations.  The above rule won't cause an
>"explosion", as it is a self-rule and we already have various rules
>involving file_type, but it isn't ideal to allow arbitrary associations
>if possible.  We ultimately want to make it easy for people to be able
>to separate what data types can exist on individual file systems using
>this control.
>
>  
>
How about if we start with customizable tiypes.

allow custonmizable self:filesystem associate;

-- 



--
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:[~2005-06-09  2:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 14:48 [Fwd: Unable to create files when using "context"option for NFS] Daniel J Walsh
2005-06-08 15:10 ` Stephen Smalley
2005-06-09  2:47   ` Daniel J Walsh [this message]

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=42A7ADD3.7060603@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=sds@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.