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
WARNING: multiple messages have this Message-ID (diff)
From: Steve Grubb <sgrubb@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-audit@redhat.com, Eric Paris <eparis@parisplace.org>,
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
--
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-07 18:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 15:43 [PATCH v3] selinux: support deferred mapping of contexts Stephen Smalley
2008-05-05 17:49 ` Stephen Smalley
2008-05-05 23:31 ` James Morris
2008-05-06 15:40 ` [PATCH v4] " Stephen Smalley
2008-05-06 20:17 ` Stephen Smalley
2008-05-06 22:31 ` James Morris
2008-05-07 12:45 ` Stephen Smalley
2008-05-07 13:45 ` James Morris
2008-05-07 15:12 ` Stephen Smalley
2008-05-07 17:03 ` [PATCH v5] " Stephen Smalley
2008-05-07 17:14 ` Stephen Smalley
2008-05-08 0:08 ` James Morris
2008-05-07 15:17 ` [PATCH v4] " Eric Paris
2008-05-07 15:23 ` Stephen Smalley
2008-05-07 15:29 ` Eric Paris
2008-05-07 15:29 ` Eric Paris
2008-05-07 16:48 ` Steve Grubb
2008-05-07 16:48 ` Steve Grubb
2008-05-07 17:20 ` Stephen Smalley
2008-05-07 17:20 ` Stephen Smalley
2008-05-07 18:45 ` Steve Grubb [this message]
2008-05-07 18:45 ` Steve Grubb
2008-05-08 15:10 ` Stephen Smalley
2008-05-08 15:10 ` Stephen Smalley
2008-05-07 17:04 ` Daniel J Walsh
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 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.