mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Mohr" <akihana@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: group ownership of tun devices -- nonfunctional?
Date: Fri, 17 Aug 2007 22:56:04 -0700	[thread overview]
Message-ID: <4746469c0708172256g164049f0qeaf02462aebd6d27@mail.gmail.com> (raw)

Per the post here:

http://lkml.org/lkml/2007/6/18/228

it appears that the group ownership patch has made it into .23.  I am
using these patches, amongst which the kernel component appears to be
identical:

http://sigxcpu.org/unsorted-patches/0001-allow-tun-ownership-by-group.patch
http://sigxcpu.org/unsorted-patches/tunctl_gid.diff

I can create devices that are owned by my user account (tunctl -u
`whoami` -t tap0) and it works fine.  However, if I use group
permissions with -g it stops working.  In all cases, if I pass -g
<group>, the interface is created correctly but it is unusable as a
non-root user.

So my question is: am I doing something wrong?  If I am, I don't see
it.  Assuming then that I am not doing anything wrong on my end, I
assume then that there is something missing from the kernel patch I
applied.  I read over it and I can't see any issues, especially
considering that tunctl comes back without error (even with -g) and
creates an interface.

Just wondering if this was an issue that should be looked into--

Mike

             reply	other threads:[~2007-08-18  5:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18  5:56 Mike Mohr [this message]
     [not found] <8Tpwf-3Nb-1@gated-at.bofh.it>
2007-08-19 16:05 ` Bodo Eggert
2007-08-19 16:10   ` Rene Herman
2007-08-19 21:42     ` Bodo Eggert
2007-08-19 23:24       ` Rene Herman
2007-08-20 11:45         ` Bodo Eggert
2007-08-22 20:42       ` Jeff Dike
2007-08-23  7:13         ` Guido Guenther

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=4746469c0708172256g164049f0qeaf02462aebd6d27@mail.gmail.com \
    --to=akihana@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®