mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <>
Cc: Roland Hieber <>
Subject: Re: [ptxdist] [APPLIED] doc: code signing: define code signing consumers
Date: Tue, 20 Jul 2021 13:49:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks, applied as 00d6be294509952a736f6d77a735dfe2583507bd.


[sent from post-receive hook]

On Tue, 20 Jul 2021 13:49:14 +0200, Roland Hieber <> wrote:
> Signed-off-by: Roland Hieber <>
> Message-Id: <>
> Signed-off-by: Michael Olbrich <>
> diff --git a/doc/dev_code_signing.rst b/doc/dev_code_signing.rst
> index 1f43f2b60ade..3fcf6866757b 100644
> --- a/doc/dev_code_signing.rst
> +++ b/doc/dev_code_signing.rst
> @@ -10,6 +10,8 @@ This is also essential when a verified boot chain is established, e.g. via
>  *High Assurance Boot* (HAB), signed FIT images, and a verified root file
>  system.
> +On the one side, **code signing consumers** are PTXdist recipes that want to
> +make use of key material, e.g. for signing kernel modules or disk images.
>  PTXdist uses `PKCS#11 <pkcs11-doc_>`_ internally to provide access to keys and
>  certificates, therefore code signing consumers should implement a PKCS#11
>  interface to make use of PTXdist's code signing infrastructure.

ptxdist mailing list
To unsubscribe, send a mail with subject "unsubscribe" to

      parent reply	other threads:[~2021-07-20 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 12:02 [ptxdist] [PATCH 1/2] " Roland Hieber
2021-07-14 12:16 ` [ptxdist] [RESEND PATCH 2/2] doc: code signing: add illustrative flowchart Roland Hieber
2021-07-14 12:58   ` [ptxdist] [PATCH] fixup! " Roland Hieber
2021-07-20 11:49   ` [ptxdist] [APPLIED] " Michael Olbrich
2021-07-20 11:49 ` Michael Olbrich [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [ptxdist] [APPLIED] doc: code signing: define code signing consumers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox