From: Phil Sutter <phil@netfilter.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Arturo Borrero Gonzalez <arturo@netfilter.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [ANNOUNCE] iptables 1.8.9 release
Date: Sun, 15 Jan 2023 23:07:44 +0100 [thread overview]
Message-ID: <Y8R5MGQTFOn2DxTb@orbyte.nwl.cc> (raw)
In-Reply-To: <Y8Onpi8LqsWIX06f@salvia>
Hi!
On Sun, Jan 15, 2023 at 08:13:42AM +0100, Pablo Neira Ayuso wrote:
> On Sat, Jan 14, 2023 at 10:18:56PM +0100, Arturo Borrero Gonzalez wrote:
> > On 1/12/23 12:20, Phil Sutter wrote:
> > > Hi!
> > >
> > > The Netfilter project proudly presents:
> > >
> > > iptables 1.8.9
> > >
> >
> > Hi Phil,
> >
> > thanks for the release!
> >
> > I see the tarball includes now a etc/xtables.conf file [0]. Could you please clarify the expected usage of this file?
> >
> > Do we intend users to have this in their systems? If so, what for.
> > It appears to be in nftables native format, so who or what mechanisms would be responsible for reading it in a system that
> > has no nftables installed?
> >
> > Perhaps the file is only useful for development purposes?
>
> I think this file just slipped through while enabling `make distcheck'
> in a recent update, but let's wait for Phil to confirm this.
Oh, I wasn't aware this file wasn't installed prior to my patches
enabling 'make dist'. This explains why Jan came up with a patch to
prevent installation. %)
So yes, this config is a leftover from an early approach of supporting a
configurable iptables-nft chain layout which never gained traction. One
should just ignore it, sorry for the mess this causes.
Cheers, Phil
prev parent reply other threads:[~2023-01-15 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:20 [ANNOUNCE] iptables 1.8.9 release Phil Sutter
2023-01-14 21:18 ` Arturo Borrero Gonzalez
2023-01-15 7:13 ` Pablo Neira Ayuso
2023-01-15 22:07 ` Phil Sutter [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=Y8R5MGQTFOn2DxTb@orbyte.nwl.cc \
--to=phil@netfilter.org \
--cc=arturo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).