From: Florian Westphal <fw@strlen.de>
To: Alan Ross <alan@sleuthco.ai>
Cc: Jan Engelhardt <ej@inai.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] libxtables: refuse to run under file capabilities
Date: Thu, 12 Feb 2026 18:20:37 +0100 [thread overview]
Message-ID: <aY4L5azyFoRua6iM@strlen.de> (raw)
In-Reply-To: <CAKgz23HD3UDEubpDfVK2dumYfTr+ODOyKmbfDunVeoPPjX2x3A@mail.gmail.com>
Alan Ross <alan@sleuthco.ai> wrote:
> Good feedback. If the binary is built with NO_SHARED_LIBS (static, no
> dlopen()), then the env vars
> never reach plugin loading, so the setcap risk is mostly gone and
> it's okay to allow it.
Not sure sure. Yes, the dlopen() risk is gone.
But I'm not convinced its safe to setcap this; are we sure there is no
bug in there that could allow to redirect control flow?
CAP_NET_ADMIN is quite powerful, I don't think we should sanction
setcap-installations in any way, so I prefer the strict version.
next prev parent reply other threads:[~2026-02-12 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 13:35 [PATCH v2] libxtables: refuse to run under file capabilities Alan Ross
2026-02-12 13:47 ` Florian Westphal
2026-02-12 16:15 ` Jan Engelhardt
2026-02-12 16:56 ` Alan Ross
2026-02-12 17:20 ` Florian Westphal [this message]
2026-02-13 11:38 ` Florian Westphal
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=aY4L5azyFoRua6iM@strlen.de \
--to=fw@strlen.de \
--cc=alan@sleuthco.ai \
--cc=ej@inai.de \
--cc=netfilter-devel@vger.kernel.org \
/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.