[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201020134208.GA297878@erythro.dev.benboeckel.internal>
Date: Tue, 20 Oct 2020 09:42:08 -0400
From: Ben Boeckel <me@...boeckel.net>
To: "Lee, Chun-Yi" <joeyli.kernel@...il.com>
Cc: David Howells <dhowells@...hat.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S . Miller" <davem@...emloft.net>, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
"Lee, Chun-Yi" <jlee@...e.com>
Subject: Re: [RFC PATCH 2/2] PKCS#7: Check codeSigning EKU for kernel module
and kexec pe verification
On Tue, Oct 20, 2020 at 14:50:01 +0800, Lee, Chun-Yi wrote:
> +config CHECK_CODESIGN_EKU
> + bool "Check codeSigning extended key usage"
> + depends on PKCS7_MESSAGE_PARSER=y
> + depends on SYSTEM_DATA_VERIFICATION
> + help
> + This option provides support for checking the codeSigning extended
> + key usage extension when verifying the signature in PKCS#7. It
> + affects kernel module verification and kexec PE binary verification
> + now.
Is the "now" necessary? Isn't it implied by the option's existence?
--Ben
Powered by blists - more mailing lists