netdev - Re: [RFC iproute2-next] remove support for iptables action

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20231224091118.2ffa84bb@hermes.local>
Date: Sun, 24 Dec 2023 09:11:18 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Florian Westphal <fw@...len.de>, Jamal Hadi Salim <hadi@...atatu.com>
Cc: netdev@...r.kernel.org
Subject: Re: [RFC iproute2-next] remove support for iptables action

On Sat, 23 Dec 2023 13:31:03 +0100
Florian Westphal <fw@...len.de> wrote:

> Stephen Hemminger <stephen@...workplumber.org> wrote:
> >  tc/em_ipset.c                        | 260 --------------  
> 
> Not sure if this is unused, also not related to the iptables/xt action.

There is both the xtables and ematch options to TC.
Jamal do you want to remove both, or some subset?

The problematic area for iproute2 seems to be the dependency on libiptables
which is not very stable. On the kernel side it is one of the places
where lightly tested integration could lead to lots of syszbot errors.