netdev - Re: Allow group ownership of TUN/TAP devices.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Feb 2009 11:54:57 +0100
From:	Guido Günther <agx@...xcpu.org>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: Allow group ownership of TUN/TAP devices.

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html