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: James Morris <jmorris@namei.org>,
	selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>
Subject: Re: [RFC][PATCH v2] selinux:  support deferred mapping of contexts
Date: Fri, 02 May 2008 11:47:59 -0400	[thread overview]
Message-ID: <481B37AF.4040806@redhat.com> (raw)
In-Reply-To: <1209649760.25678.455.camel@moss-spartans.epoch.ncsc.mil>

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

Stephen Smalley wrote:
> On Thu, 2008-05-01 at 23:22 +1000, James Morris wrote:
>> On Thu, 1 May 2008, Stephen Smalley wrote:
>>
>>> the build host with no way to define it).  Or a mechanism for a
>>> hierarchy of policies (complex, and not clear how to handle objects as
>>> they may be visible to processes operating under more than one policy,
>>> e.g. both inside and outside of the chroot).
>> Indeed, this might be helped by encoding DOIs into labels but would likely 
>> add lots of complexity and performance overhead.  AFAICT, entities in 
>> different policy namespaces would need to be totally separated (unless 
>> purely hierarchical).
> 
> Pure isolation would be cleaner, but won't work in the buildsys example,
> as there we have rpm (running outside the chroot) installing files into
> the chroot tree and then launching scriptlets within the chroot, so we
> have processes both outside and within the chroot acting on the files.
> 
> In any event, of the available alternatives, I think the
> set-unknown-label option may be the only practical one. So if you have
> any comments on the code in the patch or if you want it split into two
> stages, let me know.  Otherwise, I'll re-spin it with Casey's suggested
> change.
> 
This is half the solution.  Don't we need a new /selinux for inside the
chroot, so that when selinux-policy rpm installs the policy, it lies and
says the policy was loaded.  Then at the end of the install , restorecon
is running on the entire image to make sure the labels match the
file_context in the chroot.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkgbN68ACgkQrlYvE4MpobNNHwCg2nEftevFAgohBB7sWYe1olzk
WjQAn2BKSqmNkEaiZZrhAJZBTp32PvdC
=+3Br
-----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:[~2008-05-02 15:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:56 [RFC][PATCH v2] selinux: support deferred mapping of contexts Stephen Smalley
2008-04-30 21:51 ` Casey Schaufler
2008-05-01 10:37   ` Stephen Smalley
2008-04-30 23:06 ` James Morris
2008-05-01 11:04   ` Stephen Smalley
2008-05-01 11:41     ` Stephen Smalley
2008-05-01 14:46       ` Eric Paris
2008-05-01 15:01         ` Stephen Smalley
2008-05-01 12:11     ` James Morris
2008-05-01 12:31       ` Stephen Smalley
2008-05-01 13:22         ` James Morris
2008-05-01 13:49           ` Stephen Smalley
2008-05-02 15:47             ` Daniel J Walsh [this message]
2008-05-02 16:14               ` Stephen Smalley
2008-05-02 16:22                 ` Stephen Smalley
2008-05-02 16:45                   ` 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=481B37AF.4040806@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --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.