All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: dE <de.techno@gmail.com>, <selinux@tycho.nsa.gov>
Subject: Re: The use of fscontext(iso9660_t)
Date: Tue, 27 May 2014 08:48:45 -0400	[thread overview]
Message-ID: <538489AD.9090205@tresys.com> (raw)
In-Reply-To: <5382DCB2.3010400@gmail.com>

On 05/26/2014 02:18 AM, dE wrote:
> The obvious point of a type value for a certain FS is to restrict programs from doing things which are not allowed on that FS.
> 
> iso9660/UDF etc... is a RO FS. So writing on it should not be allowed. But I can write to files having this security context.
> 
> So what's the utility of, atleast iso9660_t?

Questions about Reference Policy should be asked on its list.

The purpose of iso9660_t is to provide a separate type for that media, not to reinforce the fact that the disks are read-only by policy.  By being a file type, certain domains can write to it since they can write to all file types.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2014-05-27 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  6:18 The use of fscontext(iso9660_t) dE
2014-05-27 12:48 ` Christopher J. PeBenito [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=538489AD.9090205@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=de.techno@gmail.com \
    --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.