From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: netfilter@vger.kernel.org,
netfilter-announce@lists.netfilter.org, lwn@lwn.net
Subject: [ANNOUNCE] libnftnl 1.2.3 release
Date: Tue, 9 Aug 2022 20:37:28 +0200 [thread overview]
Message-ID: <YvKpaFTOlsXWtS68@salvia> (raw)
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
Hi!
The Netfilter project proudly presents:
libnftnl 1.2.3
libnftnl is a userspace library providing a low-level netlink
programming interface (API) to the in-kernel nf_tables subsystem.
This library is currently used by nftables.
This release includes a compile time bugfix with clang and
-D_FORTIFY_SOURCE=2. This bug can be emulated using GCC by undefining
the __va_arg_pack macro before stdio.h
See ChangeLog that comes attached to this email for more details.
You can download it from:
https://www.netfilter.org/projects/libnftnl/downloads.html
Happy firewalling.
[-- Attachment #2: changes-libnftnl-1.2.3.txt --]
[-- Type: text/plain, Size: 139 bytes --]
Nicholas Vinson (1):
build: fix clang+glibc snprintf substitution error
Pablo Neira Ayuso (1):
build: libnftnl 1.2.3 release
reply other threads:[~2022-08-09 18:37 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=YvKpaFTOlsXWtS68@salvia \
--to=pablo@netfilter.org \
--cc=lwn@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox