[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <113544.1607090496@warthog.procyon.org.uk>
Date: Fri, 04 Dec 2020 14:01:36 +0000
From: David Howells <dhowells@...hat.com>
To: =?UTF-8?Q?Micka=c3=abl_Sala=c3=bcn?= <mic@...ikod.net>
Cc: dhowells@...hat.com, Jarkko Sakkinen <jarkko@...nel.org>,
David Woodhouse <dwmw2@...radead.org>,
"David S . Miller" <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
James Morris <jmorris@...ei.org>,
=?UTF-8?Q?Micka=c3=abl_Sala=c3=bcn?= <mic@...ux.microsoft.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
"Serge E . Hallyn" <serge@...lyn.com>, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH v1 0/9] Enable root to update the blacklist keyring
Mickaël Salaün <mic@...ikod.net> wrote:
> > What would be easiest way to smoke test the changes?
>
> An easy way to test it is to enable the second trusted keyring to
> dynamically load certificates in the kernel. Then we can create a hash
> of a valid certificate (but not loaded yet) and sign it as explained in
> tools/certs/print-cert-tbs-hash.sh (patch 9/9). Once this hash is loaded
> in the kernel, loading the blacklisted certificate will be denied. We
> can also test it with a PKCS#7 signature chain, either with the
> blacklist keyring itself, or with a signed dm-verity image.
It might also be possible to use the pkcs#7 test key type
(CONFIG_PKCS7_TEST_KEY) to aid in that.
David
Powered by blists - more mailing lists