From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2] selinux: Fix a problem with socket labels and the TUN driver
Date: Thu, 2 Jul 2009 17:39:30 -0400 [thread overview]
Message-ID: <200907021739.30279.paul.moore@hp.com> (raw)
In-Reply-To: <20090702212724.7080.70214.stgit@flek.lan>
On Thursday 02 July 2009 05:27:24 pm Paul Moore wrote:
> There is a problem where packets being sent by the TUN driver are not
> correctly handled by SELinux in the postrouting code. The issue is that
> the SELinux network access controls rely on a packet's associated sock,
> when present, for it's security label. The TUN driver does create a sock
> to send network traffic but it only calls into the LSM/SELinux code once
> via the security_sk_alloc() hook which never fully initializes the sock's
> label. This patch attempts to correct this problem by adding the normal
> LSM socket creation hooks to the TUN driver.
>
> NOTE: this is an RFC patch intended to demonstrate a possible solution
> completely different from the v1 patch, but it is still crude, untested and
> not fully hashed out just yet. Please take a look and see if this approach
> is even worth pursuing ... thanks.
> ---
>
> drivers/net/tun.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 11a0ba4..7db4b13 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -946,6 +946,10 @@ static int tun_set_iff(struct net *net, struct file
> *file, struct ifreq *ifr) if (!capable(CAP_NET_ADMIN))
> return -EPERM;
>
> + err = security_socket_create(AF_UNSPEC, SOCK_RAW, 0, 0);
> + if (err < 0)
> + return err;
> +
> /* Set dev type */
> if (ifr->ifr_flags & IFF_TUN) {
> /* TUN device */
> @@ -987,6 +991,12 @@ static int tun_set_iff(struct net *net, struct file
> *file, struct ifreq *ifr) tun->sk = sk;
> container_of(sk, struct tun_sock, sk)->tun = tun;
>
> + /* XXX - correct placement? */
> + err = security_socket_post_create(tun->socket,
> + AF_UNSPEC, SOCK_RAW, 0, 0);
That should be "&tun->socket" ... like I said, crude ...
> + if (err < 0)
> + goto err_free_sk;
> +
> tun_net_init(dev);
>
> if (strchr(dev->name, '%')) {
--
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-02 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 21:27 [RFC PATCH v2] selinux: Fix a problem with socket labels and the TUN driver Paul Moore
2009-07-02 21:39 ` Paul Moore [this message]
2009-07-06 12:58 ` Stephen Smalley
2009-07-06 20:43 ` Paul Moore
2009-07-06 21:08 ` Eric Paris
2009-07-07 11:51 ` Stephen Smalley
2009-07-07 15:40 ` 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=200907021739.30279.paul.moore@hp.com \
--to=paul.moore@hp.com \
--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.