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: <20241028164055.3059fad4@hermes.local>
Date: Mon, 28 Oct 2024 16:40:55 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: David Ahern <dsahern@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Joe
 Damato <jdamato@...tly.com>, "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?

On Mon, 28 Oct 2024 15:15:34 -0700
Jakub Kicinski <kuba@...nel.org> wrote:

> On Mon, 28 Oct 2024 15:29:35 -0600 David Ahern wrote:
> > On 10/28/24 2:58 PM, Jakub Kicinski wrote:  
> > > I was hoping for iproute2 integration a couple of years ago, but
> > > David Ahern convinced me that it's not necessary. Apparently he 
> > > changed his mind now, but I remain convinced that packaging 
> > > YNL CLI is less effort and will ensure complete coverage with
> > > no manual steps.    
> > 
> > I not recall any comment about it beyond cli.py in its current form 
> > is a total PITA to use as it lacks help and a man page.  
> 
> I can only find this thread now:
> https://lore.kernel.org/all/20240302193607.36d7a015@kernel.org/
> Could be a misunderstanding, but either way, documenting an existing
> tool seems like strictly less work than recreating it from scratch.

Is the toolset willing to maintain the backward compatibility guarantees
that iproute2 has now? Bpf support was an example of how not to do it.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ