From: "Guido Günther" <agx@sigxcpu.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Allow group ownership of TUN/TAP devices.
Date: Thu, 5 Feb 2009 11:54:57 +0100 [thread overview]
Message-ID: <20090205105456.GA26440@bogon.ms20.nix> (raw)
In-Reply-To: <498700CD.2030403@msgid.tls.msk.ru>
On Mon, Feb 02, 2009 at 05:18:53PM +0300, Michael Tokarev wrote:
[..snip..]
> My first attempt - pretty obvious when I saw -g option of tunctl - is
> to add group ownership for the tun device and add a supplementary group
> to each user (their primary group should be different). But that fails,
> since kernel only checks for egid, not any other group ids.
Since others tripped on this it might make sense to change it to also
check supplementary groups. However I don't think changing the existing
syscall is an option since it might allow users to access tun/tap
devices on existing systems that weren't allowed to do so before (which
might be a security problem).
Cheers,
-- Guido
next prev parent reply other threads:[~2009-02-05 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 14:18 Allow group ownership of TUN/TAP devices Michael Tokarev
2009-02-02 14:44 ` Michael Tokarev
2009-02-03 7:35 ` David Miller
2009-02-05 10:54 ` Guido Günther [this message]
2009-03-24 18:10 ` Michael Tokarev
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=20090205105456.GA26440@bogon.ms20.nix \
--to=agx@sigxcpu.org \
--cc=mjt@tls.msk.ru \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).