From: Joshua Brindle <method@manicmethod.com>
To: James Morris <jmorris@namei.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Speaking of networking...
Date: Wed, 27 Feb 2008 18:35:06 -0500 [thread overview]
Message-ID: <47C5F3AA.7020809@manicmethod.com> (raw)
In-Reply-To: <Xine.LNX.4.64.0802280910390.19162@us.intercode.com.au>
James Morris wrote:
> On Wed, 27 Feb 2008, Stephen Smalley wrote:
>
>
>> On Thu, 2008-02-28 at 01:01 +1100, James Morris wrote:
>>
>>> Any further thoughts on how to push the secmark integration forward?
>>>
>>> The secmark table patch should allow MAC rules to be administered
>>> independently, and I know there has been some demand for the new (well,
>>> now not so new) networking controls.
>>>
>> Has the secmark table patch gone upstream yet?
>>
>
> Nope. I think we need to know that it's going to be useful first.
>
Thats something of a chicken/egg problem. We need a separate table so
that we can peacefully co-exist with user rules before we can deploy it
widely (eg., to fedora users) to determine the viability of policy
driven secmark labeling.
On a related note CLIP has a rebuilt iptables that they should be
including in their next release because users of CLIP are very
interested in secmark labeling as well. This obviously will be in the
mangle table since they are using a RHEL5 kernel but it will still be
available.
--
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:[~2008-02-27 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 14:01 Speaking of networking James Morris
2008-02-27 14:51 ` Paul Moore
2008-02-27 15:54 ` Daniel J Walsh
2008-02-27 16:13 ` Paul Moore
2008-02-27 23:35 ` James Morris
2008-02-27 18:02 ` Stephen Smalley
2008-02-27 22:11 ` James Morris
2008-02-27 23:35 ` Joshua Brindle [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=47C5F3AA.7020809@manicmethod.com \
--to=method@manicmethod.com \
--cc=dwalsh@redhat.com \
--cc=jmorris@namei.org \
--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.