From: James Morris <jmorris@namei.org>
To: Paul Moore <paul.moore@hp.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH] LSM: Add inet_sys_snd_skb() LSM hook
Date: Fri, 21 Dec 2007 09:22:55 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0712210918170.27551@us.intercode.com.au> (raw)
In-Reply-To: <20071219222100.1626.38321.stgit@flek.americas.hpqcorp.net>
On Wed, 19 Dec 2007, Paul Moore wrote:
> Add an inet_sys_snd_skb() LSM hook to allow the LSM to provide packet level
> access control for all outbound packets. Using the existing postroute_last
> netfilter hook turns out to be problematic as it is can be invoked multiple
> times for a single packet, e.g. individual IPsec transforms, adding unwanted
> overhead and complicating the security policy.
I'm fine to ack this from a security pov -- any objections on the
networking side?
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2007-12-20 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 22:20 [RFC PATCH] New LSM hook to catch outbound packets Paul Moore
2007-12-19 22:21 ` [RFC PATCH] LSM: Add inet_sys_snd_skb() LSM hook Paul Moore
2007-12-20 22:22 ` James Morris [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=Xine.LNX.4.64.0712210918170.27551@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
/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