From: Steve Grubb <sgrubb@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eric Paris <eparis@parisplace.org>,
linux-audit@redhat.com, James Morris <jmorris@namei.org>,
selinux@tycho.nsa.gov
Subject: Re: [PATCH v4] selinux: support deferred mapping of contexts
Date: Wed, 7 May 2008 14:45:46 -0400 [thread overview]
Message-ID: <200805071445.47044.sgrubb@redhat.com> (raw)
In-Reply-To: <1210180842.6434.98.camel@moss-spartans.epoch.ncsc.mil>
On Wednesday 07 May 2008 13:20:42 Stephen Smalley wrote:
> then we'd need to define two new fields, one to correspond
> to the real/raw context string corresponding to the scontext and one to
> correspond to the real/raw context string corresponding to the tcontext.
> And they would only be present if the scontext and/or tcontext happened
> to be invalid under current policy. Maybe "rscontext" and "rtcontext"
> if we don't think that will confuse existing userspace
Sounds good to me. I don't think either names you mentioned are taken.
-Steve
next prev parent reply other threads:[~2008-05-07 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1210002195.25678.678.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <Xine.LNX.4.64.0805060930520.17367@us.intercode.com.au>
[not found] ` <1210088427.25678.771.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1210105048.25678.799.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <Xine.LNX.4.64.0805070830480.20128@us.intercode.com.au>
[not found] ` <1210164325.6434.22.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <7e0fb38c0805070817h72ac3ce7k24dc38b7eaf0ec24@mail.gmail.com>
[not found] ` <1210173806.6434.84.camel@moss-spartans.epoch.ncsc.mil>
2008-05-07 15:29 ` [PATCH v4] selinux: support deferred mapping of contexts Eric Paris
2008-05-07 16:48 ` Steve Grubb
2008-05-07 17:20 ` Stephen Smalley
2008-05-07 18:45 ` Steve Grubb [this message]
2008-05-08 15:10 ` 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=200805071445.47044.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-audit@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox