netdev - Re: ynl - mutiple policies for one nested attr used in multiple cmds

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]

Date: Fri, 4 Aug 2023 12:58:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org
Subject: Re: ynl - mutiple policies for one nested attr used in multiple
 cmds

On Fri, 4 Aug 2023 19:29:31 +0200 Jiri Pirko wrote:
> I need to have one nested attribute but according to what cmd it is used
> with, there will be different nested policy.
> 
> If I'm looking at the codes correctly, that is not currenly supported,
> correct?
> 
> If not, why idea how to format this in yaml file?

I'm not sure if you'll like it but my first choice would be to skip
the selector attribute. Put the attributes directly into the message.
There is no functional purpose the wrapping serves, right?