From: James Morris <jmorris@namei.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: [RFC][PATCH v2] selinux: support deferred mapping of contexts
Date: Thu, 1 May 2008 23:22:36 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0805012318440.4703@us.intercode.com.au> (raw)
In-Reply-To: <1209645099.25678.434.camel@moss-spartans.epoch.ncsc.mil>
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).
- James
--
James Morris
<jmorris@namei.org>
--
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.
next prev parent reply other threads:[~2008-05-01 13:22 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 [this message]
2008-05-01 13:49 ` Stephen Smalley
2008-05-02 15:47 ` Daniel J Walsh
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=Xine.LNX.4.64.0805012318440.4703@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=dwalsh@redhat.com \
--cc=eparis@parisplace.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.