From: Richard Weinberger <richard@nod.at>
To: keyrings@vger.kernel.org
Cc: Richard Weinberger <richard@nod.at>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
David Gstir <david@sigma-star.at>,
David Howells <dhowells@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Fabio Estevam <festevam@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
James Bottomley <jejb@linux.ibm.com>,
James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Mimi Zohar <zohar@linux.ibm.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
"Serge E. Hallyn" <serge@hallyn.com>,
Shawn Guo <shawnguo@kernel.org>
Subject: [PATCH 0/3] DCP as trusted keys backend
Date: Mon, 14 Jun 2021 22:16:17 +0200 [thread overview]
Message-ID: <20210614201620.30451-1-richard@nod.at> (raw)
DCP is an IP core found on NXP SoCs such as i.mx6ull.
While its bigger brother, CAAM, can directly wrap and unwrap blobs
in hardware[0], DCP offers only the bare minimum and the blob
mechanism needs aid from software.
This series adds support for a new trusted keys backend that makes use
of DCP's feature to use hardware keys which can never be read out.
[0] https://lore.kernel.org/lkml/cover.56fff82362af6228372ea82e6bd7e586e23f0966.1615914058.git-series.a.fatoum@pengutronix.de/
---
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: David Gstir <david@sigma-star.at>
Cc: David Howells <dhowells@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: James Bottomley <jejb@linux.ibm.com>
Cc: James Morris <jmorris@namei.org>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: keyrings@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-crypto@vger.kernel.org
Cc: linux-doc@vger.kernel.org
Cc: linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-security-module@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>
Cc: NXP Linux Team <linux-imx@nxp.com>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: Richard Weinberger <richard@nod.at>
Cc: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Shawn Guo <shawnguo@kernel.org>
David Gstir (1):
doc: trusted-encrypted: add DCP as new trust source
Richard Weinberger (2):
crypto: mxs-dcp: Add support for hardware provided keys
KEYS: trusted: Introduce support for NXP DCP-based trusted keys
.../admin-guide/kernel-parameters.txt | 1 +
.../security/keys/trusted-encrypted.rst | 84 ++++-
MAINTAINERS | 9 +
drivers/crypto/mxs-dcp.c | 110 +++++-
include/keys/trusted_dcp.h | 13 +
include/linux/mxs-dcp.h | 19 +
security/keys/trusted-keys/Makefile | 1 +
security/keys/trusted-keys/trusted_core.c | 6 +-
security/keys/trusted-keys/trusted_dcp.c | 325 ++++++++++++++++++
9 files changed, 554 insertions(+), 14 deletions(-)
create mode 100644 include/keys/trusted_dcp.h
create mode 100644 include/linux/mxs-dcp.h
create mode 100644 security/keys/trusted-keys/trusted_dcp.c
--
2.26.2
next reply other threads:[~2021-06-14 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 20:16 Richard Weinberger [this message]
2021-06-14 20:16 ` [PATCH 1/3] crypto: mxs-dcp: Add support for hardware provided keys Richard Weinberger
2021-06-25 12:21 ` Richard Weinberger
2021-06-25 12:28 ` Herbert Xu
2021-06-25 13:12 ` Richard Weinberger
2021-07-14 9:24 ` Ahmad Fatoum
2021-07-14 10:39 ` Richard Weinberger
2021-07-14 11:01 ` Ahmad Fatoum
2021-06-14 20:16 ` [PATCH 2/3] KEYS: trusted: Introduce support for NXP DCP-based trusted keys Richard Weinberger
2021-07-14 9:29 ` Ahmad Fatoum
2021-07-14 10:44 ` Richard Weinberger
2021-07-21 17:17 ` Ahmad Fatoum
2021-06-14 20:16 ` [PATCH 3/3] doc: trusted-encrypted: add DCP as new trust source Richard Weinberger
2021-07-14 9:32 ` Ahmad Fatoum
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=20210614201620.30451-1-richard@nod.at \
--to=richard@nod.at \
--cc=a.fatoum@pengutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=david@sigma-star.at \
--cc=dhowells@redhat.com \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=kernel@pengutronix.de \
--cc=keyrings@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=serge@hallyn.com \
--cc=shawnguo@kernel.org \
--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).