From: James Morris <jmorris@namei.org>
To: Jan Engelhardt <jengelh@medozas.de>
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 0/2] Security: Add security tables for mandatory access control
Date: Thu, 22 May 2008 08:43:48 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0805220842570.8393@us.intercode.com.au> (raw)
In-Reply-To: <alpine.LNX.1.10.0805212359590.15136@fbirervta.pbzchgretzou.qr>
On Thu, 22 May 2008, Jan Engelhardt wrote:
>
> On Wednesday 2008-05-21 16:17, James Morris wrote:
> >
> >In a nutshell, the need for this arises from the fact that MAC labeling
> >rules utilizing iptables via SECMARK and CONNSECMARK are not subject to
> >discretionary security policy (i.e. not even "root" or a user with
> >CAP_NET_ADMIN may be able to modify these rules).
>
> Yet I do not see any code to possibly prohibit changing the table.
There are calls from SECMARK and CONNSECMARK into the SELinux API, which
are the labeling targets.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-05-21 22:43 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
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 [this message]
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=Xine.LNX.4.64.0805220842570.8393@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=jengelh@medozas.de \
--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