From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@tycho.nsa.gov
Subject: Re: The problem with TUN/TAP devices
Date: Wed, 1 Jul 2009 18:58:22 -0400 [thread overview]
Message-ID: <200907011858.22635.paul.moore@hp.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0907020841540.32336@tundra.namei.org>
On Wednesday 01 July 2009 06:42:36 pm James Morris wrote:
> On Wed, 1 Jul 2009, Paul Moore wrote:
> > Well, if we can't do it in sk_alloc() then I think we are stuck with a
> > new hook; which just seems wrong.
>
> Why isn't the TUN driver calling the same code as other socket creating
> code?
The other socket creating code handles the final setup/initialization in the
security_socket_post_create() hook which operates on sockets not socks.
--
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.
next prev parent reply other threads:[~2009-07-01 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 21:34 The problem with TUN/TAP devices Paul Moore
2009-06-30 22:19 ` James Morris
2009-07-01 15:06 ` Paul Moore
2009-07-01 3:32 ` Casey Schaufler
2009-07-01 15:11 ` Paul Moore
2009-07-01 13:44 ` Stephen Smalley
2009-07-01 15:01 ` Eric Paris
2009-07-01 15:06 ` Stephen Smalley
2009-07-01 15:19 ` Paul Moore
2009-07-01 15:42 ` Stephen Smalley
2009-07-01 16:34 ` Paul Moore
2009-07-01 22:42 ` James Morris
2009-07-01 22:58 ` Paul Moore [this message]
2009-07-01 23:53 ` James Morris
2009-07-02 16:58 ` Paul Moore
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=200907011858.22635.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--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.