All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: I would like to change the behavior of MCS label creations in directory.
Date: Thu, 22 Sep 2011 15:53:23 -0400	[thread overview]
Message-ID: <4E7B9233.6080609@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently if I create a directory labeled

etc_t:s0:c1

And with a process running as unconfined_t:s0-s0:c0.c1023 create a
file within the directory, the file gets created with the label
etc_t:s0.   I would like to change the behavior to creating the file
as etc_t:s0:c1.

That way an administrator could modify files within a sandbox and have
the files be labeled correctly.

I believe this behavior differs from MLS but believe this would be
what the admin expects.

Is changing this a kernel or policy issue?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk57kjMACgkQrlYvE4MpobO6GACgrZnzZl4OySYUkZATfl7RJPWb
z1YAn0m4wkHLWYWlR6urpuQ0tuGb+cdN
=uDm1
-----END PGP SIGNATURE-----

--
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:[~2011-09-22 19:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 19:53 Daniel J Walsh [this message]
2011-09-22 20:13 ` I would like to change the behavior of MCS label creations in directory Guido Trentalancia
2011-09-22 20:31 ` Stephen Smalley
2011-09-22 20:32   ` Daniel J Walsh
2011-09-22 20:37     ` Stephen Smalley
2011-09-22 20:42       ` Stephen Smalley
2011-09-23 15:01         ` Daniel J Walsh
2011-09-23 15:07           ` Stephen Smalley
2011-09-23 16:06             ` Guido Trentalancia
2011-09-23 17:33               ` Daniel J Walsh
2011-09-24 22:05             ` David Windsor
2011-09-27 16:06               ` Stephen Smalley
2011-09-27 16:50                 ` David Windsor
2011-09-27 16:51                   ` Stephen Smalley
2011-09-27 18:13                 ` Daniel J Walsh
2011-10-14 15:57                   ` Daniel J Walsh
2011-10-18 12:34                     ` Christopher J. PeBenito
     [not found]                       ` <00243337-937e-4e6b-880b-ba2f351112e7@email.android.com>
2011-10-18 22:07                         ` David Windsor
2011-10-19 16:55                           ` Stephen Smalley
2011-10-19 15:31                       ` Joshua Brindle
2011-10-19 16:26                         ` Stephen Smalley
2011-11-22 18:59                           ` Eric Paris
2011-11-22 19:25                             ` Stephen Smalley
2011-11-22 19:37                               ` Eric Paris
2011-11-22 19:39                                 ` Stephen Smalley
2011-11-22 19:42                                   ` Eric Paris
2011-10-19 16:36                         ` Kyle Moffett
2011-10-19 17:41                         ` Daniel J Walsh
2011-10-19 17:47                           ` Joshua Brindle
2011-10-19 17:50                             ` Daniel J Walsh
2011-09-22 20:41 ` Guido Trentalancia

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=4E7B9233.6080609@redhat.com \
    --to=dwalsh@redhat.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.