linux-kernel - Re: [PATCH net-next] tun: fix group permission check

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]

Message-Id: 
 <173362262925.3130221.16243033138491486291.git-patchwork-notify@kernel.org>
Date: Sun, 08 Dec 2024 01:50:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stas Sergeev <stsp2@...dex.ru>
Cc: netdev@...r.kernel.org, willemdebruijn.kernel@...il.com,
 jasowang@...hat.com, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] tun: fix group permission check

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Thu,  5 Dec 2024 10:36:14 +0300 you wrote:
> Currently tun checks the group permission even if the user have matched.
> Besides going against the usual permission semantic, this has a
> very interesting implication: if the tun group is not among the
> supplementary groups of the tun user, then effectively no one can
> access the tun device. CAP_SYS_ADMIN still can, but its the same as
> not setting the tun ownership.
> 
> [...]

Here is the summary with links:
  - [net-next] tun: fix group permission check
    https://git.kernel.org/netdev/net-next/c/3ca459eaba1b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html