All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	David Howells <dhowells@redhat.com>,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	keyrings@vger.kernel.org
Subject: [GIT PULL] trusted keys changes for v6.10-rc1
Date: Thu,  9 May 2024 18:47:51 +0300	[thread overview]
Message-ID: <20240509154751.25983-1-jarkko@kernel.org> (raw)

  Merge tag '6.9-rc7-ksmbd-fixes' of git://git.samba.org/ksmbd (2024-05-08 10:39:53 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/keys-trusted-next-6.10-rc1

for you to fetch changes up to 28c5f596ae3d1790cdc96fa5fc7370f934abfb2e:

  docs: trusted-encrypted: add DCP as new trust source (2024-05-09 18:29:03 +0300)

----------------------------------------------------------------
Hi,

This is pull request for trusted keys subsystem containing a new key
type for the Data Co-Processor (DCP), which is an IP core built into
many NXP SoCs such as i.mx6ull.

BR, Jarkko

----------------------------------------------------------------
David Gstir (6):
      crypto: mxs-dcp: Add support for hardware-bound keys
      KEYS: trusted: improve scalability of trust source config
      KEYS: trusted: Introduce NXP DCP-backed trusted keys
      MAINTAINERS: add entry for DCP-based trusted keys
      docs: document DCP-backed trusted keys kernel params
      docs: trusted-encrypted: add DCP as new trust source

 Documentation/admin-guide/kernel-parameters.txt   |  13 +
 Documentation/security/keys/trusted-encrypted.rst |  53 ++++
 MAINTAINERS                                       |   9 +
 drivers/crypto/mxs-dcp.c                          | 104 ++++++-
 include/keys/trusted_dcp.h                        |  11 +
 include/soc/fsl/dcp.h                             |  20 ++
 security/keys/trusted-keys/Kconfig                |  18 +-
 security/keys/trusted-keys/Makefile               |   2 +
 security/keys/trusted-keys/trusted_core.c         |   6 +-
 security/keys/trusted-keys/trusted_dcp.c          | 332 ++++++++++++++++++++++
 10 files changed, 554 insertions(+), 14 deletions(-)
 create mode 100644 include/keys/trusted_dcp.h
 create mode 100644 include/soc/fsl/dcp.h
 create mode 100644 security/keys/trusted-keys/trusted_dcp.c

             reply	other threads:[~2024-05-09 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 15:47 Jarkko Sakkinen [this message]
2024-05-13 17:50 ` [GIT PULL] trusted keys changes for v6.10-rc1 pr-tracker-bot

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=20240509154751.25983-1-jarkko@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.