From: patchwork-bot+netdevbpf@kernel.org
To: David Woodhouse <dwmw2@infradead.org>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
jasowangio@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, omosnace@redhat.com, stsp2@yandex.ru,
luto@kernel.org
Subject: Re: [PATCH v3] tun: Require CAP_NET_ADMIN to attach to an ownerless device
Date: Thu, 22 Oct 2026 01:10:08 +0000 [thread overview]
Message-ID: <179263140807.1392288.12458500793289522283.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3c77f88acff5b3c2617b22d64faad15f6212619c.camel@infradead.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Oct 2026 10:48:10 +0100 you wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> Twenty years ago I made creating a tuntap device require CAP_NET_ADMIN
> in commit ca6bb5d7ab22 ("[NET]: Require CAP_NET_ADMIN to create tuntap
> devices.")
>
> The idea was to allow the permissions on /dev/net/tun to be relaxed to
> 0666 and thus allow owners of tun devices assigned with TUNSETOWNER to
> actually open it and get at their devices.
>
> [...]
Here is the summary with links:
- [v3] tun: Require CAP_NET_ADMIN to attach to an ownerless device
https://git.kernel.org/netdev/net/c/ffdf678dd166
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-22 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:48 [PATCH v3] tun: Require CAP_NET_ADMIN to attach to an ownerless device David Woodhouse
2026-10-20 13:47 ` Willem de Bruijn
2026-10-22 1:10 ` patchwork-bot+netdevbpf [this message]
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=179263140807.1392288.12458500793289522283.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=luto@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnace@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox