From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 14 Jul 2021 14:03:28 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1m3dbs-00058J-0y for lore@lore.pengutronix.de; Wed, 14 Jul 2021 14:03:28 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1m3dbr-0002AD-K5; Wed, 14 Jul 2021 14:03:27 +0200 Received: from dude.hi.pengutronix.de ([2001:67c:670:100:1d::7]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m3dbD-00029p-CR; Wed, 14 Jul 2021 14:02:47 +0200 Received: from rhi by dude.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1m3dbD-0004E6-45; Wed, 14 Jul 2021 14:02:47 +0200 From: Roland Hieber To: ptxdist@pengutronix.de Date: Wed, 14 Jul 2021 14:02:33 +0200 Message-Id: <20210714120234.16196-1-rhi@pengutronix.de> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Mail-Followup-To: Roland Hieber , ptxdist@pengutronix.de Subject: [ptxdist] [PATCH 1/2] doc: code signing: define code signing consumers X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: Roland Hieber Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Signed-off-by: Roland Hieber --- 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 `_ 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