From: Eric Snowberg <eric.snowberg@oracle.com>
To: zohar@linux.ibm.com, dhowells@redhat.com, dwmw2@infradead.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
dmitry.kasatkin@gmail.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, jlee@suse.com,
eric.snowberg@oracle.com, kanth.ghatraju@oracle.com,
konrad.wilk@oracle.com, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [PATCH 0/3] Add digitalSignature enforcement keyring restrictions
Date: Mon, 8 May 2023 18:07:05 -0400 [thread overview]
Message-ID: <20230508220708.2888510-1-eric.snowberg@oracle.com> (raw)
X.509 certificates may contain a key usage extension [1]. The key usage
extension defines the purpose of the certificate. One area of
interest is the digitalSignature. The digitalSignature usage is
typically used for code signing (integrity).
Within the "Add CA enforcement key restrictions" [2] series, the
digitalSignature is being saved. This series builds upon the previous
one and adds restrictions based on the digitalSignature usage.
A new keyring restriction called restrict_link_by_digsig is added. The new
restriction only allows keys that contain digitalSignature usage within
it.
The first two keyrings to use this restriction are the .ima and .evm
keyrings. With this update, only keys containing a digitalSignature
will be allowed in either keyring.
1. https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.3
2. https://lore.kernel.org/all/20230329220231.h6afgarrvdlwwdjc@kernel.org/T/
Eric Snowberg (3):
KEYS: DigitalSignature link restriction
integrity: Enforce digitalSignature usage in the ima and evm keyrings
integrity: Remove EXPERIMENTAL from Kconfig
certs/system_keyring.c | 52 +++++++++++++++++++++++++++++++
crypto/asymmetric_keys/restrict.c | 44 ++++++++++++++++++++++++++
include/crypto/public_key.h | 11 +++++++
include/keys/system_keyring.h | 11 +++++++
security/integrity/digsig.c | 4 +--
security/integrity/evm/Kconfig | 3 +-
security/integrity/ima/Kconfig | 5 +--
7 files changed, 125 insertions(+), 5 deletions(-)
base-commit: ac9a78681b921877518763ba0e89202254349d1b
--
2.27.0
next reply other threads:[~2023-05-08 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 22:07 Eric Snowberg [this message]
2023-05-08 22:07 ` [PATCH 1/3] KEYS: DigitalSignature link restriction Eric Snowberg
2023-05-10 22:34 ` Jarkko Sakkinen
2023-05-11 22:48 ` Eric Snowberg
2023-05-17 1:18 ` Mimi Zohar
2023-05-08 22:07 ` [PATCH 2/3] integrity: Enforce digitalSignature usage in the ima and evm keyrings Eric Snowberg
2023-05-17 1:18 ` Mimi Zohar
2023-05-08 22:07 ` [PATCH 3/3] integrity: Remove EXPERIMENTAL from Kconfig Eric Snowberg
2023-05-10 22:42 ` Jarkko Sakkinen
2023-05-17 1:18 ` Mimi Zohar
2023-05-10 22:31 ` [PATCH 0/3] Add digitalSignature enforcement keyring restrictions Jarkko Sakkinen
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=20230508220708.2888510-1-eric.snowberg@oracle.com \
--to=eric.snowberg@oracle.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jlee@suse.com \
--cc=jmorris@namei.org \
--cc=kanth.ghatraju@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).