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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 5 Aug 2022 16:32:30 +0000
From:   "Keller, Jacob E" <>
To:     Jakub Kicinski <>
CC:     Jiri Pirko <>,
        "" <>
Subject: RE: [net-next PATCH 1/2] devlink: add dry run attribute to flash


> -----Original Message-----
> From: Jakub Kicinski <>
> Sent: Monday, July 25, 2022 6:14 PM
> To: Keller, Jacob E <>
> Cc: Jiri Pirko <>;
> Subject: Re: [net-next PATCH 1/2] devlink: add dry run attribute to flash update
> Hm, yes. Don't invest too much effort into rendering per-cmd policies
> right now, tho. I've started working on putting the parsing policies
> in YAML last Friday. This way we can auto-gen the policy for the kernel
> and user space can auto-gen the parser/nl TLV writer. Long story short
> we can kill two birds with one stone if you hold off until I have the
> format ironed out. For now maybe just fork the policies into two -
> with and without dry run attr. We'll improve the granularity later
> when doing the YAML conversion.

Any update on this?

FWIW I started looking at iproute2 code to dump policy and check whether a specific attribute is accepted by the kernel.


Powered by blists - more mailing lists