From: Patrick McHardy <kaber@trash.net>
To: James Morris <jmorris@namei.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>, Paul Moore <paul.moore@hp.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH 3/4] add support for modifying secmark via ctnetlink
Date: Wed, 21 May 2008 14:00:09 +0200 [thread overview]
Message-ID: <48340EC9.3020507@trash.net> (raw)
In-Reply-To: <Xine.LNX.4.64.0805212129150.19104@us.intercode.com.au>
James Morris wrote:
> On Wed, 21 May 2008, Patrick McHardy wrote:
>
>> Pablo Neira Ayuso wrote:
>>> As for now we only support dumping. This patch adds support to change
>>> the secmark from ctnetlink.
>>>
>> I'm wondering whether this isn't subverting the intent of
>> secmark since AFAIK SELinux doesn't have finegrained
>> controls for netlink messages. OTOH, it also doesn't have
>> finegrained control over iptables rulesets.
>>
>> James, does this patch look OK to you?
>
> There is some fine-grained netlink coverage, but it is incomplete (the
> various generic netlink layers likely need to be consolidated first).
>
> Currently, the SECMARK and CONNSECMARK targets call out to
> selinux_secmark_relabel_packet_permission() when SELinux is active to
> obtain a permission check. So, detection of the current security model
> would need to be similarly performed.
Thanks for the explanation.
> The bigger issue perhaps is whether there's really a need to set secmark
> via ctnetlink.
I think Pablo wants to use it for synchronization with conntrackd,
but I'm not sure.
next prev parent reply other threads:[~2008-05-21 12:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 22:29 [PATCH 3/4] add support for modifying secmark via ctnetlink Pablo Neira Ayuso
2008-05-21 11:15 ` Patrick McHardy
2008-05-21 11:42 ` James Morris
2008-05-21 12:00 ` Patrick McHardy [this message]
2008-05-21 16:46 ` Paul Moore
2008-05-21 16:54 ` Stephen Smalley
2008-05-21 17:13 ` Patrick McHardy
2008-05-22 18:11 ` Stephen Smalley
2008-05-22 19:08 ` Patrick McHardy
2008-05-21 17:41 ` Paul Moore
2008-05-21 17:11 ` Patrick McHardy
2008-05-21 17:51 ` Paul Moore
2008-05-21 17:55 ` Stephen Smalley
2008-05-21 19:03 ` Pablo Neira Ayuso
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=48340EC9.3020507@trash.net \
--to=kaber@trash.net \
--cc=jmorris@namei.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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