linux-kernel - Re: [PATCH v13 0/4] Intel MAX10 BMC Secure Update Driver

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] [day] [month] [year] [list]

Message-ID: <65ed311d-a492-413e-33a8-f64e9c41e7c2@redhat.com>
Date:   Wed, 28 Jul 2021 07:56:16 -0700
From:   Tom Rix <trix@...hat.com>
To:     Russ Weight <russell.h.weight@...el.com>, mdf@...nel.org,
        linux-fpga@...r.kernel.org, linux-kernel@...r.kernel.org,
        "Wu, Hao" <hao.wu@...el.com>
Cc:     lgoncalv@...hat.com, yilun.xu@...el.com, matthew.gerlach@...el.com,
        richard.gong@...el.com
Subject: Re: [PATCH v13 0/4] Intel MAX10 BMC Secure Update Driver

Russ
> Russ Weight (4):
>    fpga: m10bmc-sec: create max10 bmc secure update driver
>    fpga: m10bmc-sec: expose max10 flash update count
>    fpga: m10bmc-sec: expose max10 canceled keys in sysfs

Since sec-mgr is taking a long time, I am looking at splitting out parts 
we can agree on.

These 3 patches are a new dfl specific driver and do not depend on sec-mgr.

Here is a poc on char-misc-next, splitting them and moving them before 
sec-mgr

https://github.com/trixirt/linux-next/commits/sec-mgr-reorder

Moritz, Hao

Could these 3 patches go into fpga-next now ?

Tom


>    fpga: m10bmc-sec: add max10 secure update functions