From: Paul Moore <paul.moore@hp.com>
To: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: [PATCH 0/2] New LSM hooks for the TUN driver
Date: Fri, 28 Aug 2009 18:12:36 -0400 [thread overview]
Message-ID: <20090828220400.3900.64377.stgit@flek.lan> (raw)
This is the third, and hopefully final, version of the new LSM TUN hooks. This
version incorporates all outstanding feedback as well as my sign-off and ACKs
from both Eric and Serge (see patches). However, the patches are still missing
an ACK from netdev - I haven't heard any objections but I'm not certain anyone
from netdev has really taken a look yet.
Dave and James - these patches once again straddle that line between networking
and security; while James has usually ushered these types of patches upstream
in the past I'll let you two fight it out again for the honors (assuming you
are both okay with the patches).
The patches can also be found in git form here:
* git://git.infradead.org/users/pcmoore/lblnet-2.6_next
Thanks.
---
Paul Moore (2):
selinux: Support for the new TUN LSM hooks
lsm: Add hooks to the TUN driver
drivers/net/tun.c | 22 +++++++---
include/linux/security.h | 31 ++++++++++++++
security/capability.c | 19 +++++++++
security/security.c | 18 ++++++++
security/selinux/hooks.c | 60 +++++++++++++++++++++++++++-
security/selinux/include/av_inherit.h | 1
security/selinux/include/av_permissions.h | 22 ++++++++++
security/selinux/include/class_to_string.h | 1
security/selinux/include/flask.h | 1
9 files changed, 166 insertions(+), 9 deletions(-)
next reply other threads:[~2009-08-28 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 22:12 Paul Moore [this message]
2009-08-28 22:12 ` [PATCH 1/2] lsm: Add hooks to the TUN driver Paul Moore
2009-08-28 22:46 ` David Miller
2009-08-31 11:42 ` James Morris
2009-08-28 22:12 ` [PATCH 2/2] selinux: Support for the new TUN LSM hooks Paul Moore
2009-09-01 1:16 ` [PATCH 0/2] New LSM hooks for the TUN driver 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=20090828220400.3900.64377.stgit@flek.lan \
--to=paul.moore@hp.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).