From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, James Morris <jmorris@namei.org>,
Joshua Brindle <method@manicmethod.com>,
dwalsh@redhat.com
Subject: Re: [RFC] SELinux: use SECINITSID_NETMSG instead of SECINITSID_UNLABELED for NetLabel
Date: Mon, 23 Apr 2007 16:40:10 -0400 [thread overview]
Message-ID: <200704231640.10821.paul.moore@hp.com> (raw)
In-Reply-To: <1177360618.24282.107.camel@moss-spartans.epoch.ncsc.mil>
On Monday 23 April 2007 4:36:58 pm Stephen Smalley wrote:
> On Mon, 2007-04-23 at 14:56 -0400, Paul Moore wrote:
> > The next logical questions are first, does anyone have a good idea on how
> > to solve these compatibility breaks? Second, assuming there is not an
> > easy fix, do people consider the issues above to be deal breakers?
>
> It sounds as though it has a very limited scope (MLS & NetLabel), and
> the kernel/policy mismatch is less likely in that environment (as
> changing the kernel or the policy would require re-evaluation, and in
> particular, the policy change modifies the MLS constraints). So
> possibly just a matter of documenting the dependency between the kernel
> version and the policy version for MLS.
Okay, that sounds good to me.
Thanks.
--
paul moore
linux security @ hp
--
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.
prev parent reply other threads:[~2007-04-23 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 2:50 [RFC] SELinux: use SECINITSID_NETMSG instead of SECINITSID_UNLABELED for NetLabel Paul Moore
2007-03-19 3:12 ` Joshua Brindle
2007-03-19 19:03 ` Stephen Smalley
2007-03-20 17:58 ` Paul Moore
2007-03-20 18:43 ` Stephen Smalley
2007-03-20 21:34 ` Paul Moore
2007-03-21 12:20 ` Stephen Smalley
2007-03-21 22:42 ` Paul Moore
2007-04-23 18:56 ` Paul Moore
2007-04-23 20:36 ` Stephen Smalley
2007-04-23 20:40 ` Paul Moore [this message]
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=200704231640.10821.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=dwalsh@redhat.com \
--cc=jmorris@namei.org \
--cc=method@manicmethod.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.