All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Eric Paris <eparis@parisplace.org>
Cc: linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
	selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 2/2] selinux: Support for the new TUN LSM hooks
Date: Wed, 12 Aug 2009 10:59:50 -0400	[thread overview]
Message-ID: <200908121059.50167.paul.moore@hp.com> (raw)
In-Reply-To: <7e0fb38c0908111336uadf57efx7d87be7761c0e138@mail.gmail.com>

On Tuesday 11 August 2009 04:36:22 pm Eric Paris wrote:
> On Mon, Aug 10, 2009 at 1:28 PM, Paul Moore<paul.moore@hp.com> wrote:
> > Add support for the new TUN LSM hooks: security_tun_dev_create(),
> > security_tun_dev_post_create() and security_tun_dev_attach().  This
> > includes the addition of a new object class, tun_socket, which represents
> > the socks associated with TUN devices.  The _tun_dev_create() and
> > _tun_dev_post_create() hooks are fairly similar to the standard socket
> > functions but _tun_dev_attach() is a bit special.  The _tun_dev_attach()
> > is unique because it involves a domain attaching to an existing TUN
> > device and its associated tun_socket object, an operation which does not
> > exist with standard sockets and most closely resembles a relabel
> > operation.
>
> Looks good to me, feel free to add my Ack

Thanks, I added both acks.

-- 
paul moore
linux @ hp


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul.moore@hp.com>
To: Eric Paris <eparis@parisplace.org>
Cc: linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
	selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 2/2] selinux: Support for the new TUN LSM hooks
Date: Wed, 12 Aug 2009 10:59:50 -0400	[thread overview]
Message-ID: <200908121059.50167.paul.moore@hp.com> (raw)
In-Reply-To: <7e0fb38c0908111336uadf57efx7d87be7761c0e138@mail.gmail.com>

On Tuesday 11 August 2009 04:36:22 pm Eric Paris wrote:
> On Mon, Aug 10, 2009 at 1:28 PM, Paul Moore<paul.moore@hp.com> wrote:
> > Add support for the new TUN LSM hooks: security_tun_dev_create(),
> > security_tun_dev_post_create() and security_tun_dev_attach().  This
> > includes the addition of a new object class, tun_socket, which represents
> > the socks associated with TUN devices.  The _tun_dev_create() and
> > _tun_dev_post_create() hooks are fairly similar to the standard socket
> > functions but _tun_dev_attach() is a bit special.  The _tun_dev_attach()
> > is unique because it involves a domain attaching to an existing TUN
> > device and its associated tun_socket object, an operation which does not
> > exist with standard sockets and most closely resembles a relabel
> > operation.
>
> Looks good to me, feel free to add my Ack

Thanks, I added both acks.

-- 
paul moore
linux @ hp


  reply	other threads:[~2009-08-12 14:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 17:28 [RFC PATCH v2 0/2] New LSM hooks for the TUN driver Paul Moore
2009-08-10 17:28 ` Paul Moore
2009-08-10 17:28 ` [RFC PATCH v2 1/2] lsm: Add hooks to " Paul Moore
2009-08-10 17:28   ` Paul Moore
2009-08-11 20:34   ` Eric Paris
2009-08-11 20:34     ` Eric Paris
2009-08-12 19:28   ` Serge E. Hallyn
2009-08-12 19:28     ` Serge E. Hallyn
2009-08-12 19:43     ` Paul Moore
2009-08-12 19:43       ` Paul Moore
2009-08-10 17:28 ` [RFC PATCH v2 2/2] selinux: Support for the new TUN LSM hooks Paul Moore
2009-08-10 17:28   ` Paul Moore
2009-08-11 20:36   ` Eric Paris
2009-08-11 20:36     ` Eric Paris
2009-08-12 14:59     ` Paul Moore [this message]
2009-08-12 14:59       ` Paul Moore
2009-08-12 22:14   ` Serge E. Hallyn
2009-08-12 22:14     ` Serge E. Hallyn
2009-08-12 22:55     ` Paul Moore
2009-08-12 22:55       ` Paul Moore
2009-08-12 23:07       ` Serge E. Hallyn
2009-08-12 23:07         ` Serge E. Hallyn

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=200908121059.50167.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=eparis@parisplace.org \
    --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 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.