From: Patrick McHardy <kaber@trash.net>
To: James Morris <jmorris@namei.org>
Cc: netfilter-devel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Paul Moore <paul.moore@hp.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH 1/2] Security: Add iptables security table for mandatory access control rules
Date: Wed, 21 May 2008 19:18:04 +0200 [thread overview]
Message-ID: <4834594C.5030704@trash.net> (raw)
In-Reply-To: <Xine.LNX.4.64.0805220017511.3033@us.intercode.com.au>
James Morris wrote:
> The following patch implements a new "security" table for iptables, so
> that MAC (SELinux etc.) networking rules can be managed separately to
> standard DAC rules.
>
> This is to help with distro integration of the new secmark-based
> network controls, per various previous discussions.
>
> The need for a separate table arises from the fact that existing tools
> and usage of iptables will likely clash with centralized MAC policy
> management.
>
> The SECMARK and CONNSECMARK targets will still be valid in the mangle
> table to prevent breakage of existing users.
Thanks James, just one question:
> --- a/net/ipv4/netfilter/Kconfig
> +++ b/net/ipv4/netfilter/Kconfig
> @@ -365,6 +365,17 @@ config IP_NF_RAW
> If you want to compile it as a module, say M here and read
> <file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
>
> +# security table for MAC policy
> +config IP_NF_SECURITY
> + tristate "Security table"
> + depends on IP_NF_IPTABLES
> + default m if NETFILTER_ADVANCED=n
Is the table also useful without CONFIG_SECURITY? Otherwise
I'd suggest to add a dependency.
next prev parent reply other threads:[~2008-05-21 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 14:17 [PATCH 0/2] Security: Add security tables for mandatory access control James Morris
2008-05-21 14:18 ` [PATCH 1/2] Security: Add iptables security table for mandatory access control rules James Morris
2008-05-21 17:18 ` Patrick McHardy [this message]
2008-05-21 17:22 ` Patrick McHardy
2008-05-21 22:44 ` James Morris
2008-05-22 12:15 ` Patrick McHardy
2008-07-17 3:41 ` James Morris
2008-07-17 8:25 ` Patrick McHardy
2008-05-21 14:19 ` [PATCH 2/2] Security: Add ip6tables security table James Morris
2008-05-21 17:23 ` Patrick McHardy
2008-05-21 22:01 ` [PATCH 0/2] Security: Add security tables for mandatory access control Jan Engelhardt
2008-05-21 22:43 ` James Morris
2008-05-22 15:57 ` Jan Engelhardt
2008-05-26 8:06 ` James Morris
2008-05-26 8:23 ` Jan Engelhardt
2008-05-26 9:12 ` James Morris
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=4834594C.5030704@trash.net \
--to=kaber@trash.net \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox