From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [iptables PATCH 0/4] Some misc fixes
Date: Wed, 4 May 2022 12:34:12 +0200 [thread overview]
Message-ID: <20220504103416.19712-1-phil@nwl.cc> (raw)
Fix and improve DNAT printing routines, add some missing bits to
extension man page and further improve extension loading for
unprivileged users.
Phil Sutter (4):
extensions: DNAT: Merge core printing functions
man: *NAT: Review --random* option descriptions
extensions: LOG: Document --log-macdecode in man page
nft: Fix EPERM handling for extensions without rev 0
extensions/libxt_DNAT.c | 58 +++++++++----------
extensions/libxt_DNAT.man | 4 +-
extensions/libxt_LOG.man | 3 +
extensions/libxt_MASQUERADE.man | 10 +---
extensions/libxt_REDIRECT.man | 4 +-
extensions/libxt_SNAT.man | 8 +--
iptables/nft.c | 14 +++--
.../testcases/iptables/0008-unprivileged_0 | 6 ++
8 files changed, 52 insertions(+), 55 deletions(-)
--
2.34.1
next reply other threads:[~2022-05-04 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 10:34 Phil Sutter [this message]
2022-05-04 10:34 ` [iptables PATCH 1/4] extensions: DNAT: Merge core printing functions Phil Sutter
2022-05-04 10:34 ` [iptables PATCH 2/4] man: *NAT: Review --random* option descriptions Phil Sutter
2022-05-04 10:34 ` [iptables PATCH 3/4] extensions: LOG: Document --log-macdecode in man page Phil Sutter
2022-05-04 10:34 ` [iptables PATCH 4/4] nft: Fix EPERM handling for extensions without rev 0 Phil Sutter
2022-05-04 20:17 ` Pablo Neira Ayuso
2022-05-05 12:09 ` Phil Sutter
2022-05-05 13:30 ` Pablo Neira Ayuso
2022-05-06 11:43 ` [iptables PATCH v2 " Phil Sutter
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=20220504103416.19712-1-phil@nwl.cc \
--to=phil@nwl.cc \
--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).