netdev - Re: [PATCH iproute2] vxlan: add support for flowlab inherit

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: <fa8e2b04-5ddf-4121-be34-c57690f06c63@gmail.com>
Date: Fri, 26 Jan 2024 10:17:36 -0700
From: David Ahern <dsahern@...il.com>
To: Vincent Bernat <vincent@...nat.ch>, Ido Schimmel <idosch@...sch.org>,
 Alce Lafranque <alce@...ranque.net>
Cc: netdev@...r.kernel.org, stephen@...workplumber.org
Subject: Re: [PATCH iproute2] vxlan: add support for flowlab inherit

On 1/25/24 11:28 PM, Vincent Bernat wrote:
> Honestly, I have a hard time finding a real downside. The day we need to
> specify both a value and a policy, it will still be time to introduce a
> new keyword. For now, it seems better to be consistent with the other
> protocols and with the other keywords (ttl, for example) using the same
> approach.

ok. let's move forward without the new keyword with the understanding it
is not perfect, but at least consistent across commands should a problem
arise. Consistency allows simpler workarounds.