[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKfDRXixb3WoNkBBY9_y77QyydLnjfp9QxO1TniShO+T1O3+Mg@mail.gmail.com>
Date: Thu, 2 May 2019 10:09:56 +0200
From: Kristian Evensen <kristian.evensen@...il.com>
To: Florian Westphal <fw@...len.de>
Cc: Nicolas Dichtel <nicolas.dichtel@...nd.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
Hi,
On Thu, May 2, 2019 at 9:46 AM Florian Westphal <fw@...len.de> wrote:
>
> 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
> restrict this.
I agree with both of you. Unless anyone beats me to it, I will try to
have a fix ready during the weekend.
BR,
Kristian
Powered by blists - more mailing lists