All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stas Sergeev <stsp2@yandex.ru>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
	jasowang@redhat.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tun: fix group permission check
Date: Sun, 08 Dec 2024 01:50:29 +0000	[thread overview]
Message-ID: <173362262925.3130221.16243033138491486291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241205073614.294773-1-stsp2@yandex.ru>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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



  parent reply	other threads:[~2024-12-08  1:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  7:36 [PATCH net-next] tun: fix group permission check Stas Sergeev
2024-12-05 16:50 ` Willem de Bruijn
2024-12-06  2:42   ` Jason Wang
2024-12-08  1:44 ` Jakub Kicinski
2024-12-08  1:44   ` Jakub Kicinski
2024-12-08  6:53   ` stsp
2024-12-09 21:44     ` Jakub Kicinski
2024-12-09 21:53       ` stsp
2024-12-08  1:50 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-17  9:05 Stas Sergeev
2024-11-17 15:04 ` Willem de Bruijn
2024-11-18 21:40   ` Willem de Bruijn
2024-11-19 10:51     ` Paolo Abeni
2024-11-19 10:54       ` stsp
2024-11-19  9:42   ` stsp
2024-11-19 14:56     ` Willem de Bruijn

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=173362262925.3130221.16243033138491486291.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stsp2@yandex.ru \
    --cc=willemdebruijn.kernel@gmail.com \
    /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.