From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter <netfilter@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Cc: netdev@vger.kernel.org, netfilter-announce@lists.netfilter.org,
lwn@lwn.net
Subject: [ANNOUNCE] nftables 1.0.4 release
Date: Tue, 7 Jun 2022 16:41:43 +0200 [thread overview]
Message-ID: <Yp9jp9XwOtcNaBCe@salvia> (raw)
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Hi!
The Netfilter project proudly presents:
nftables 1.0.4
This is an incremental release accumulating bugfixes for two
regressions that were introduced in 1.0.3:
* Fix segfault in -o/--optimize with unsupported statements:
http://git.netfilter.org/nftables/commit/?id=59bd944f6d75e99fe0c8d743e7fd482672640c2d
* Bogus datatype mismatch error report in sets:
http://git.netfilter.org/nftables/commit/?id=818f7dded9c9e8a89a2de98801425536180ae307
You can download this new release from:
https://www.netfilter.org/projects/nftables/downloads.html
https://www.netfilter.org/pub/nftables/
To build the code, libnftnl >= 1.2.2 and libmnl >= 1.0.4 are required:
* https://netfilter.org/projects/libnftnl/index.html
* https://netfilter.org/projects/libmnl/index.html
Visit our wikipage for user documentation at:
* https://wiki.nftables.org
For the manpage reference, check man(8) nft.
In case of bugs and feature request, file them via:
* https://bugzilla.netfilter.org
Happy firewalling.
[-- Attachment #2: changes-nftables-1.0.4.txt --]
[-- Type: text/plain, Size: 297 bytes --]
Pablo Neira Ayuso (5):
optimize: segfault when releasing unsupported statement
tests: shell: sets_with_ifnames release netns on exit
evaluate: reset ctx->set after set interval evaluation
tests: shell: remove leftover modules on cleanup
build: Bump version to 1.0.4
reply other threads:[~2022-06-07 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Yp9jp9XwOtcNaBCe@salvia \
--to=pablo@netfilter.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-announce@lists.netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--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 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.