netdev - Re: yaml gen NL families support in iproute2?

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: <61184cdf-6afc-4b9b-a3d2-b5f8478e3cbb@kernel.org>
Date: Thu, 17 Oct 2024 12:36:47 -0600
From: David Ahern <dsahern@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>,
 Stephen Hemminger <stephen@...workplumber.org>,
 "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?

On 10/17/24 11:41 AM, Paolo Abeni wrote:
> Hi all,
> 
> please allow me to [re?]start this conversation.
> 
> I think it would be very useful to bring yaml gennl families support in
> iproute2, so that end-users/admins could consolidated
> administration/setup in a single tool - as opposed to current status
> where something is only doable with iproute2 and something with the
> yml-cli tool bundled in the kernel sources.
> 
> Code wise it could be implemented extending a bit the auto-generated
> code generation to provide even text/argument to NL parsing, so that the
> iproute-specific glue (and maintenance effort) could be minimal.
> 
> WDYT?
> 

I would like to see the yaml files integrated into iproute2, but I have
not had time to look into doing it.

I have been using the cli.py tool a lot in the past few months and I
have it klunky and hard to use - especially around valid options for get
and dump requests.

Coping yaml files into iproute2 is the trivial part; we already do that
for uapi header files. The harder part is properly integrating the
commands into the package. To me requirements are along the lines of:
- aligning with iproute2 style of commands,
- a man page per command,
- proper help options to guide users

The last 2 should include attributes that can be added to get and dump
requests.