From: Patrick McHardy <kaber@trash.net>
To: James Morris <jmorris@namei.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Stephen Smalley <sds@tycho.nsa.gov>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH][RFC] Security marking
Date: Mon, 17 Apr 2006 20:55:20 +0200 [thread overview]
Message-ID: <4443E498.4010301@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604171440480.17563@d.namei>
James Morris wrote:
> On Mon, 17 Apr 2006, Patrick McHardy wrote:
>
>
>>>From a pure netfilter POV it would still be nice to have the socket
>>hooks for userspace queueing in socket context and filtering hard
>>to track protocols. My only question is: if I would port the skfilter
>>patches to the current kernel today and fix the unresolved issues,
>>would you still prefer this approach?
>
>
> I think the newer model of marking the packets first via Netfilter then
> interpreting them at the socket layer is superior. i.e. skfilter is
> probably not preferred for SELinux now.
>
> However, it's still useful for incoming user matching for things like
> user-level firewalling.
OK, thanks. I plan to make it ready for submission eventually, just
wanted to make sure I'm not holding back things.
next prev parent reply other threads:[~2006-04-17 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 5:10 [PATCH][RFC] Security marking James Morris
2006-04-16 5:28 ` James Morris
2006-04-17 17:51 ` Patrick McHardy
2006-04-17 18:43 ` James Morris
2006-04-17 18:55 ` Patrick McHardy [this message]
2006-04-19 22:49 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 18:40 edwin
2006-04-18 1:01 ` 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=4443E498.4010301@trash.net \
--to=kaber@trash.net \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--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 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.