linux-kernel - Re: [PATCH v5 0/2] Add support for ECDSA-signed kernel modules

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:   Wed, 9 Jun 2021 09:58:29 -0400
From:   Stefan Berger <stefanb@...ux.ibm.com>
To:     Jarkko Sakkinen <jarkko@...nel.org>
Cc:     jeyu@...nel.org, keyrings@...r.kernel.org, dhowells@...hat.com,
        dwmw2@...radead.org, zohar@...ux.ibm.com, nayna@...ux.ibm.com,
        linux-integrity@...r.kernel.org,
        linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/2] Add support for ECDSA-signed kernel modules

On 6/9/21 8:44 AM, Jarkko Sakkinen wrote:
> On Thu, Jun 03, 2021 at 08:32:59AM -0400, Stefan Berger wrote:
>> On 6/3/21 2:47 AM, Jarkko Sakkinen wrote:
>>>> -- 
>>>> 2.29.2
>>>>
>>>>
>>> Please instead send a fix.
>> We have a Fixes tag in 1/2, so we want this to propagate to older kernels
>> and need the fix in 1/2 for that reason.
>>
>>     Stefan
> So please do an additional fix and send it.

1/2 is supposed to propagate to older kernels and needs to change as 
posted here in v5 (assuming that this does indeed fix what the build bot 
was complaining about). 2/2 also changes. A fix on top of v4 would fix 
2/2 but won't apply cleanly to 1/2 as cannot easily propagate to older 
kernels. Is that what we want? Why can you not remove v4 from your queue 
and replace it with v5?

    Stefan