From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Paul Moore <paul.moore@hp.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: Time to remove compat_net?
Date: Mon, 03 Sep 2007 11:02:26 -0400 [thread overview]
Message-ID: <1188831746.2876.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200708301633.33632.paul.moore@hp.com>
On Thu, 2007-08-30 at 16:33 -0400, Paul Moore wrote:
> On Thursday, August 30 2007 4:12:24 pm Stephen Smalley wrote:
> > On Thu, 2007-08-30 at 16:07 -0400, Paul Moore wrote:
> > > Does anyone have any objections to placing the compat_net code on the
> > > kernel's "feature removal schedule" (I'd go for removal in 2/2008, six
> > > months from now)? SECMARK can do everything that the older compat_net
> > > controls can do, and it does it with less overhead and a cleaner
> > > implementation.
> >
> > I'd be happy to see it go (conditional checks considered harmful), but a
> > good starting point would be to get secmark turned on in Fedora (it was
> > still off last I looked) and verify that nothing breaks.
> >
> > We also don't have any tools capable of managing secmark today; with the
> > legacy controls, we could labels ports and netifs via semanage. Only
> > secmark userland integration to date has been the basic iptables command
> > line support.
>
> Okay RedHat guys ... are there any plans to migrate semanage over to using the
> SECMARK controls?
I have argued in the past that making semanage handle secmark is the
wrong approach. Basically - the whole point of using secmark is that you
get the full power of iptables. If we force updates through semanage
then you either a) recreate all of iptables in semanage or b) seriously
cripple the mechanism through a restricted interface.
> If not, what do you need (besides patches to semanage) to
> make the transition?
>
What more do you mean other than setting compat_net to 0?
Karl
--
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:[~2007-09-03 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 20:07 Time to remove compat_net? Paul Moore
2007-08-30 20:12 ` Stephen Smalley
2007-08-30 20:33 ` Paul Moore
2007-09-03 15:02 ` Karl MacMillan [this message]
2007-09-04 0:37 ` Joshua Brindle
2007-09-04 11:38 ` Paul Moore
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=1188831746.2876.3.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=paul.moore@hp.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.