Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Richard Van Tassel <richard.van.tassel.work@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: userns packet mangling
Date: Sat, 17 Oct 2026 00:51:05 +0200	[thread overview]
Message-ID: <atKqWQwqM3AW7pil@strlen.de> (raw)
In-Reply-To: <CAGLc8_RABvE42M_1icBskniznt5-e2QLNd7g3Fku3bcw+2aE2Q@mail.gmail.com>

Richard Van Tassel <richard.van.tassel.work@gmail.com> wrote:
> Hello, netfilter world.
> 
> I am very curious about the status of re-enabling packet mangling in
> user namespaces.
> 
> I understand that it takes time to find and address security concerns,
> and I hope the netfilter community takes all the time they need. That
> being said, I just wanted to echo the appetite for that functionality
> to return, similar to
> 582d218b638be68342dd80893c41746b35c1be76.camel@student.kit.edu (sorry
> if I'm linking this incorrectly, I haven't used this sort of mailing
> list before)
 
> I am currently working around the disabling in a somewhat controlled
> fashion using a custom kernel patch and module to allow a process in
> init ns with CAP_NET_ADMIN to grant permission to mangle on a per-ns
> basis. As I understand the situation currently, I don't think there's
> much appetite for accepting this workaround as a kernel contribution,
> since the disabling is meant to be temporary. But I feel like I should
> mention it nevertheless.

https://patchwork.ozlabs.org/project/netfilter-devel/patch/20260905050150.30273-1-fw@strlen.de/

is still pending, and its closing known security hole.
So no, for now we can't re-enable this feature.

  reply	other threads:[~2026-10-16 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 20:18 userns packet mangling Richard Van Tassel
2026-10-16 22:51 ` Florian Westphal [this message]
2026-10-17  9:04   ` Pablo Neira Ayuso

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=atKqWQwqM3AW7pil@strlen.de \
    --to=fw@strlen.de \
    --cc=netfilter@vger.kernel.org \
    --cc=richard.van.tassel.work@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