From: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, "Lee, Chun-Yi" <jlee@suse.com>
Subject: [RFC PATCH 0/2] Check codeSigning extended key usage extension
Date: Tue, 20 Oct 2020 14:49:59 +0800 [thread overview]
Message-ID: <20201020065001.13836-1-jlee@suse.com> (raw)
NIAP PP_OS certification requests that the OS shall validate the
CodeSigning extended key usage extension field for integrity
verifiction of exectable code:
https://www.niap-ccevs.org/MMO/PP/-442-/
FIA_X509_EXT.1.1
This patchset adds the logic for parsing the codeSigning EKU extension
field in X.509. And checking the CodeSigning EKU when verifying signature
of kernel module or kexec PE binary in PKCS#7.
Lee, Chun-Yi (2):
X.509: Add CodeSigning extended key usage parsing
PKCS#7: Check codeSigning EKU for kernel module and kexec pe
verification
certs/system_keyring.c | 2 +-
crypto/asymmetric_keys/Kconfig | 10 +++++++++
crypto/asymmetric_keys/pkcs7_trust.c | 37 ++++++++++++++++++++++++++++---
crypto/asymmetric_keys/x509_cert_parser.c | 24 ++++++++++++++++++++
include/crypto/pkcs7.h | 3 ++-
include/crypto/public_key.h | 1 +
include/linux/oid_registry.h | 5 +++++
7 files changed, 77 insertions(+), 5 deletions(-)
--
2.16.4
next reply other threads:[~2020-10-20 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 6:49 Lee, Chun-Yi [this message]
2020-10-20 6:50 ` [RFC PATCH 1/2] X.509: Add CodeSigning extended key usage parsing Lee, Chun-Yi
2020-10-20 6:50 ` [RFC PATCH 2/2] PKCS#7: Check codeSigning EKU for kernel module and kexec pe verification Lee, Chun-Yi
2020-10-20 13:42 ` Ben Boeckel
2020-10-20 14:56 ` Randy Dunlap
2020-10-21 10:20 ` joeyli
2020-10-21 10:10 ` joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201020065001.13836-1-jlee@suse.com \
--to=joeyli.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jlee@suse.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox