netdev - Re: [PATCH v6 5/6] doc/netlink: nftables: Add getcompat operation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <UQH3L3tF4h7c1fSG9jiwLDOlbwlsoqbmP_3oKD-sjVhUZB0YoSEy0TUD5DZ09eLwxVu55xOuEJ5wDx5pWBROF0VAWQvwdYNmw8KEGxzvvnA=@protonmail.com>
Date: Tue, 27 Jan 2026 13:22:47 +0000
From: "Remy D. Farley" <one-d-wide@...tonmail.com>
To: Florian Westphal <fw@...len.de>
Cc: Donald Hunter <donald.hunter@...il.com>, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, Pablo Neira Ayuso <pablo@...filter.org>, Jozsef Kadlecsik <kadlec@...filter.org>, Phil Sutter <phil@....cc>, netfilter-devel@...r.kernel.org, coreteam@...filter.org
Subject: Re: [PATCH v6 5/6] doc/netlink: nftables: Add getcompat operation

On Tuesday, January 27th, 2026 at 13:00, Florian Westphal <fw@...len.de> wrote:

> Remy D. Farley one-d-wide@...tonmail.com wrote:
> 
> > > Its used by compatibility mode, it requires an nft binary linked
> > > to libxtables, native nftables doesn't need it.
> > > 
> > > I would prefer not to mention its existence.
> > 
> > Ah, I see. Netlink-bindings have a tool to decode netlink communication, so
> > it's a bit awkward to show a bunch of unkown-operations on a common command.
> > I'm fine keeping it downstream.
> 
> 
> No, showing unknown-operations is even worse.
> Maybe just document in commit message that this is to avoid
> clutter and present something more readable.
> 
> And perhaps mention that this is only for iptables-nft in the yaml file too.
> (nft uses it on 'nft list' only if it encounters a rule added by iptables-nft).

Do you mean to still add getcompat operation to spec in the kernel tree?
In case I misrepresented it, netlink-bindings is not a kernel project. And
AFACT, this issue isn't relevant for ynl C library, as it would only try to
decodes messages from operations you sent.

https://github.com/one-d-wide/netlink-bindings