netdev - Re: [PATCH iproute2] ip route: get: only set RTM_F_LOOKUP

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: <20190114080547.452b9915@hermes.lan>
Date:   Mon, 14 Jan 2019 08:05:47 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc:     dsahern@...il.com, netdev@...r.kernel.org,
        oss-drivers@...ronome.com
Subject: Re: [PATCH iproute2] ip route: get: only set RTM_F_LOOKUP_TABLE
 flag for IPv4

On Sat, 12 Jan 2019 12:54:06 -0800
Jakub Kicinski <jakub.kicinski@...ronome.com> wrote:

> Kernel ignores the RTM_F_LOOKUP_TABLE flag for all families
> but IPv4.  Don't set it, otherwise it may fall foul of
> strict checking policies.
> 
> Signed-off-by: Jakub Kicinski <jakub.kicinski@...ronome.com>

Doing the right thing is a good idea, but really I can't see
the point of doing this. The kernel will always have to accept
requests from older versions of iproute2 (it can never be stricter)
because of ABI compatibility. So unless you can make a stronger
case for this; no not applying it.