From: Peter Hoeg <peter@hoeg.com>
To: netfilter@vger.kernel.org
Subject: Re: Running nft --check as non-root
Date: Fri, 12 Aug 2022 13:15:41 +0800 [thread overview]
Message-ID: <87v8qy9gzg.fsf@hoeg.com> (raw)
In-Reply-To: <20220811161500.GF8667@breakpoint.cc>
> Yes, this not a syntax check. The ruleset is passed to the kernel.
Is there any other way we can verify that at least the syntax is valid? Maybe have a --syntax flag that just invokes the scanner and parser without needing any privileged access?
I know nothing of the internals, so that might of course be completely impossible given the current architecture.
prev parent reply other threads:[~2022-08-12 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 15:53 Running nft --check as non-root Peter Hoeg
2022-08-11 16:15 ` Florian Westphal
2022-08-12 5:15 ` Peter Hoeg [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=87v8qy9gzg.fsf@hoeg.com \
--to=peter@hoeg.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox