public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel•org>
To: "David Gstir" <david@sigma-star•at>,
	"Mimi Zohar" <zohar@linux•ibm.com>,
	"James Bottomley" <jejb@linux•ibm.com>,
	"Herbert Xu" <herbert@gondor•apana.org.au>,
	"David S. Miller" <davem@davemloft•net>
Cc: linux-doc@vger•kernel.org,
	Catalin Marinas <catalin.marinas@arm•com>,
	David Howells <dhowells@redhat•com>,
	keyrings@vger•kernel.org, Fabio Estevam <festevam@gmail•com>,
	Ahmad Fatoum <a.fatoum@pengutronix•de>,
	Paul Moore <paul@paul-moore•com>,
	Jonathan Corbet <corbet@lwn•net>,
	Richard Weinberger <richard@nod•at>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel•com>,
	James Morris <jmorris@namei•org>,
	NXP Linux Team <linux-imx@nxp•com>,
	"Serge E. Hallyn" <serge@hallyn•com>,
	"Paul E. McKenney" <paulmck@kernel•org>,
	Sascha Hauer <s.hauer@pengutronix•de>,
	sigma star Kernel Team <upstream+dcp@sigma-star•at>,
	"Steven Rostedt \(Google\)" <rostedt@goodmis•org>,
	David Oberhollenzer <david.oberhollenzer@sigma-star•at>,
	linux-arm-kernel@lists•infradead.org,
	linuxppc-dev@lists•ozlabs.org,
	Randy Dunlap <rdunlap@infradead•org>,
	linux-kernel@vger•kernel.org, Li Yang <leoyang.li@nxp•com>,
	linux-security-module@vger•kernel.org,
	linux-crypto@vger•kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix•de>,
	Tejun Heo <tj@kernel•org>,
	linux-integrity@vger•kernel.org, Shawn Guo <shawnguo@kernel•org>
Subject: Re: [PATCH v6 5/6] docs: document DCP-backed trusted keys kernel params
Date: Thu, 07 Mar 2024 21:32:08 +0200	[thread overview]
Message-ID: <CZNRO3HH6T0W.R91RSALY7S88@kernel.org> (raw)
In-Reply-To: <20240307153842.80033-6-david@sigma-star.at>

On Thu Mar 7, 2024 at 5:38 PM EET, David Gstir wrote:
> Document the kernel parameters trusted.dcp_use_otp_key
> and trusted.dcp_skip_zk_test for DCP-backed trusted keys.
>
> Co-developed-by: Richard Weinberger <richard@nod•at>
> Signed-off-by: Richard Weinberger <richard@nod•at>
> Co-developed-by: David Oberhollenzer <david.oberhollenzer@sigma-star•at>
> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star•at>
> Signed-off-by: David Gstir <david@sigma-star•at>
> ---
>  Documentation/admin-guide/kernel-parameters.txt | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 24c02c704049..b6944e57768a 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -6698,6 +6698,7 @@
>  			- "tpm"
>  			- "tee"
>  			- "caam"
> +			- "dcp"
>  			If not specified then it defaults to iterating through
>  			the trust source list starting with TPM and assigns the
>  			first trust source as a backend which is initialized
> @@ -6713,6 +6714,18 @@
>  			If not specified, "default" is used. In this case,
>  			the RNG's choice is left to each individual trust source.
>  
> +	trusted.dcp_use_otp_key
> +			This is intended to be used in combination with
> +			trusted.source=dcp and will select the DCP OTP key
> +			instead of the DCP UNIQUE key blob encryption.
> +
> +	trusted.dcp_skip_zk_test
> +			This is intended to be used in combination with
> +			trusted.source=dcp and will disable the check if all
> +			the blob key is zero'ed. This is helpful for situations where
> +			having this key zero'ed is acceptable. E.g. in testing
> +			scenarios.
> +
>  	tsc=		Disable clocksource stability checks for TSC.
>  			Format: <string>
>  			[x86] reliable: mark tsc clocksource as reliable, this

I don't disagree with the API part.

Mimi?

BR, Jarkko

  reply	other threads:[~2024-03-07 19:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 15:38 [PATCH v5 0/6] DCP as trusted keys backend David Gstir
2024-03-07 15:38 ` [PATCH v6 1/6] crypto: mxs-dcp: Add support for hardware-bound keys David Gstir
2024-03-07 19:17   ` Jarkko Sakkinen
2024-03-07 15:38 ` [PATCH v6 2/6] KEYS: trusted: improve scalability of trust source config David Gstir
2024-03-07 19:18   ` Jarkko Sakkinen
2024-03-07 15:38 ` [PATCH v6 3/6] KEYS: trusted: Introduce NXP DCP-backed trusted keys David Gstir
2024-03-07 19:23   ` Jarkko Sakkinen
2024-03-07 19:30   ` Jarkko Sakkinen
2024-03-08  7:17     ` David Gstir
2024-03-11 20:07       ` Jarkko Sakkinen
2024-03-07 15:38 ` [PATCH v6 4/6] MAINTAINERS: add entry for DCP-based " David Gstir
2024-03-07 15:38 ` [PATCH v6 5/6] docs: document DCP-backed trusted keys kernel params David Gstir
2024-03-07 19:32   ` Jarkko Sakkinen [this message]
2024-03-07 15:38 ` [PATCH v6 6/6] docs: trusted-encrypted: add DCP as new trust source David Gstir

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=CZNRO3HH6T0W.R91RSALY7S88@kernel.org \
    --to=jarkko@kernel$(echo .)org \
    --cc=a.fatoum@pengutronix$(echo .)de \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=corbet@lwn$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=david.oberhollenzer@sigma-star$(echo .)at \
    --cc=david@sigma-star$(echo .)at \
    --cc=dhowells@redhat$(echo .)com \
    --cc=festevam@gmail$(echo .)com \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=jejb@linux$(echo .)ibm.com \
    --cc=jmorris@namei$(echo .)org \
    --cc=kernel@pengutronix$(echo .)de \
    --cc=keyrings@vger$(echo .)kernel.org \
    --cc=leoyang.li@nxp$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-imx@nxp$(echo .)com \
    --cc=linux-integrity@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-security-module@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=paul@paul-moore$(echo .)com \
    --cc=paulmck@kernel$(echo .)org \
    --cc=rafael.j.wysocki@intel$(echo .)com \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=richard@nod$(echo .)at \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=s.hauer@pengutronix$(echo .)de \
    --cc=serge@hallyn$(echo .)com \
    --cc=shawnguo@kernel$(echo .)org \
    --cc=tj@kernel$(echo .)org \
    --cc=upstream+dcp@sigma-star$(echo .)at \
    --cc=zohar@linux$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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