[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4f2df82-be23-ed46-79f5-749adc3c52c3@6wind.com>
Date: Thu, 2 May 2019 10:27:17 +0200
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: Florian Westphal <fw@...len.de>
Cc: Kristian Evensen <kristian.evensen@...il.com>,
Pablo Neira Ayuso <pablo@...filter.org>,
Netfilter Development Mailing list
<netfilter-devel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>
Subject: Re: [PATCH 07/31] netfilter: ctnetlink: Support L3 protocol-filter on
flush
Le 02/05/2019 à 09:46, Florian Westphal a écrit :
> Nicolas Dichtel <nicolas.dichtel@...nd.com> wrote:
>> I understand your point, but this is a regression. Ignoring a field/attribute of
>> a netlink message is part of the uAPI. This field exists for more than a decade
>> (probably two), so you cannot just use it because nobody was using it. Just see
>> all discussions about strict validation of netlink messages.
>> Moreover, the conntrack tool exists also for ages and is an official tool.
>
> FWIW I agree with Nicolas, we should restore old behaviour and flush
> everything when AF_INET is given. We can add new netlink attr to
To avoid regression, we sould ignore it, AF_INET or not.
> restrict this.
Yes.
Powered by blists - more mailing lists