mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 1/2] doc: code signing: define code signing consumers
Date: Wed, 14 Jul 2021 14:02:33 +0200
Message-ID: <20210714120234.16196-1-rhi@pengutronix.de> (raw)

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 doc/dev_code_signing.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/dev_code_signing.rst b/doc/dev_code_signing.rst
index 56ac0e3b3217..5a6196cb2826 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.
-- 
2.30.2


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


             reply	other threads:[~2021-07-14 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 12:02 Roland Hieber [this message]
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 ` [ptxdist] [APPLIED] doc: code signing: define code signing consumers Michael Olbrich

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=20210714120234.16196-1-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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

mailarchive of the ptxdist mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://lore.ptxdist.org/ptxdist/0 ptxdist/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ptxdist ptxdist/ https://lore.ptxdist.org/ptxdist \
		ptxdist@pengutronix.de
	public-inbox-index ptxdist

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git