linux-kernel - Re: [PATCH] certs: Reference revocation list for all keyrings

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: <d622f47e5446f71571170ef72be43ea0a89e5d48.camel@linux.ibm.com>
Date:   Fri, 14 Jul 2023 18:11:12 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Eric Snowberg <eric.snowberg@...cle.com>, dhowells@...hat.com,
        jarkko@...nel.org, dwmw2@...radead.org
Cc:     keyrings@...r.kernel.org, linux-kernel@...r.kernel.org,
        kanth.ghatraju@...cle.com, konrad.wilk@...cle.com
Subject: Re: [PATCH] certs: Reference revocation list for all keyrings

On Tue, 2023-01-17 at 12:15 -0500, Eric Snowberg wrote:
> Systems booted with shim have a Forbidden Signature Database called mokx.
> During boot, hashes and certs contained within the mokx are loaded into the
> blacklist keyring.  When calling verify_pkcs7_message_sig the contents of
> the blacklist keyring (or revocation list) are referenced when validating
> keys on the platform keyring. Currently, when validating against the
> secondary or builtin keyrings, the revocation list is not referenced.  Move
> up the check to allow the revocation list to be used with all keyrings,
> including the secondary and builtin, allowing the system owner to take
> corrective action should a vulnerability be found within keys contained
> within either keyring.
> 
> Signed-off-by: Eric Snowberg <eric.snowberg@...cle.com>

Reviewed-by: Mimi Zohar <zohar@...ux.ibm.com>