From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@namei.org>,
KaiGai Kohei <kaigai@ak.jp.nec.com>,
selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [PATCH v4 2/2] selinux: generate flask headers during kernel build
Date: Thu, 1 Oct 2009 09:46:28 -0400 [thread overview]
Message-ID: <200910010946.28121.paul.moore@hp.com> (raw)
In-Reply-To: <1254400360.30591.105.camel@moss-pluto.epoch.ncsc.mil>
On Thursday 01 October 2009 08:32:40 am Stephen Smalley wrote:
> On Thu, 2009-10-01 at 07:46 +1000, James Morris wrote:
> > On Wed, 30 Sep 2009, Stephen Smalley wrote:
> > > Does anyone think we still need to support policy versions <
> > > POLICYDB_VERSION_NLCLASS (18)? If not, then we can just drop the
> > > dynamic remapping of netlink classes in the security server:
> > > if (policydb_loaded_version < POLICYDB_VERSION_NLCLASS)
> > > if (tclass >= SECCLASS_NETLINK_ROUTE_SOCKET &&
> > > tclass <= SECCLASS_NETLINK_DNRT_SOCKET)
> > > tclass = SECCLASS_NETLINK_SOCKET;
> > >
> > > I think RHEL4 shipped with policy.18.
> >
> > Was any distro shipped with a lower policy version? If not, then I think
> > it should be ok.
>
> policy.18 was first supported by Linux 2.6.8.
> I think the only distro to ship with SELinux enabled and Linux < 2.6.8
> would have been Fedora Core 2, which is long since EOL'd and even akpm
> doesn't run it anymore. Not sure about Hardened Gentoo - Chris and/or
> Joshua? Debian selinux packages predated Fedora, of course, but weren't
> mainstreamed into Debian until much later.
>
> I didn't yet remove this logic in my patches, but will do so if there
> are no objections.
I'm sure you've already thought about this, but if you do remove the code for
policy versions below 18 I would recommend doing so in a standalone patch -
that way if somebody does end up with a broken system the bisect will only
drag down the policy.18 patch and not the rest of these patches (which are
going to be a very nice addition).
--
paul moore
linux @ 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.
next prev parent reply other threads:[~2009-10-01 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 17:09 [PATCH v4 1/2] selinux: dynamic class/perm discovery Stephen Smalley
2009-09-29 17:14 ` [PATCH v4 2/2] selinux: generate flask headers during kernel build Stephen Smalley
2009-09-29 18:03 ` Stephen Smalley
2009-09-29 18:52 ` Stephen Smalley
2009-09-30 3:00 ` KaiGai Kohei
2009-09-30 2:32 ` KaiGai Kohei
2009-09-30 12:39 ` Stephen Smalley
2009-09-30 12:53 ` Stephen Smalley
2009-09-30 21:46 ` James Morris
2009-10-01 12:32 ` Stephen Smalley
2009-10-01 12:55 ` Joshua Brindle
2009-10-01 13:46 ` Paul Moore [this message]
2009-10-01 15:31 ` Stephen Smalley
2009-10-03 0:33 ` Chris PeBenito
2009-10-03 18:30 ` 欧珂塔维亚
2009-09-30 13:54 ` Stephen Smalley
2009-09-30 14:47 ` Stephen Smalley
2009-09-30 15:10 ` Stephen Smalley
2009-09-30 15:25 ` Stephen Smalley
2009-09-30 16:40 ` 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=200910010946.28121.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cpebenito@tresys.com \
--cc=eparis@parisplace.org \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=kaigai@ak.jp.nec.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.