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
| ||
|
Date: Wed, 29 Jul 2020 16:59:48 -0700 From: Jacob Keller <jacob.e.keller@...el.com> To: Jakub Kicinski <kuba@...nel.org> Cc: Jiri Pirko <jiri@...nulli.us>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Tom Herbert <tom@...bertland.com>, Jiri Pirko <jiri@...lanox.com>, Jonathan Corbet <corbet@....net>, Michael Chan <michael.chan@...adcom.com>, Bin Luo <luobin9@...wei.com>, Saeed Mahameed <saeedm@...lanox.com>, Leon Romanovsky <leon@...nel.org>, Ido Schimmel <idosch@...lanox.com>, Danielle Ratson <danieller@...lanox.com> Subject: Re: [RFC PATCH net-next v2 6/6] devlink: add overwrite mode to flash update On 7/29/2020 4:16 PM, Jakub Kicinski wrote: > On Wed, 29 Jul 2020 15:49:05 -0700 Jacob Keller wrote: >> The security revision is tied into the management firmware image and >> would always be updated when an image is updated, but the minimum >> revision is only updated on an explicit request request. > > Does it have to be updated during FW flashing? Can't it be a devlink > param? > Oh, right. I'd forgotten about that type of parameter. Makes sense. I'll implement the current security revision as a component of flash info (so that it can be reported via devlink info, and can't be changed) but the minimum should be able to be a parameter just fine. Thanks, Jake
Powered by blists - more mailing lists