From: Michael Olbrich <mol@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: dev_code_signing: add "Managing Certificate Authority Keyrings"
Date: Fri, 26 Jun 2020 13:00:55 +0200 [thread overview]
Message-ID: <E1jom6J-0006N9-1C@dude02.hi.pengutronix.de> (raw)
In-Reply-To: <20200624160849.6966-2-bst@pengutronix.de>
Thanks, applied as 846c8b91bb0eb7d136995c2d045f44640d407b89.
Michael
[sent from post-receive hook]
On Fri, 26 Jun 2020 13:00:55 +0200, Bastian Krause <bst@pengutronix.de> wrote:
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> Message-Id: <20200624160849.6966-2-bst@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/dev_code_signing.rst b/doc/dev_code_signing.rst
> index fbebb6b524e1..d47002e8c380 100644
> --- a/doc/dev_code_signing.rst
> +++ b/doc/dev_code_signing.rst
> @@ -107,6 +107,32 @@ Switching the code signing provider is now finally possible with
> ``ptxdist platformconfig``, then navigate to *Code signing* → *Code signing
> provider*.
>
> +.. _code_signing_ca_keyrings:
> +
> +Managing Certificate Authority Keyrings
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +In case a self-signed certificate is used :ref:`cs_append_ca_from_uri` can
> +be called to add the certificate from the (Soft)HSM.
> +
> +To allow rollovers multiple certificates can be added by calling the
> +``cs_append_ca_*`` functions multiple times.
> +Depending on if the certificate resides on a (Soft)HSM or in a file the
> +appropriate functions must be called.
> +
> +More complex public key infrastructures (PKIs) consist of separated CA and
> +*end-entity*.
> +The CA certificate is only available as a file, the private key is stored in a
> +safe and inaccessible location (from the build system's perspective).
> +The signing key as well as the corresponding certificate are stored on an HSM.
> +Only the CA certificate should end up in the keyring, so
> +:ref:`cs_append_ca_from_der` or :ref:`cs_append_ca_from_pem` must be used to
> +append it to the keyring.
> +
> +Some HSMs do not support storing certificates at all.
> +In these cases the certificate is present as a file and must be appended with
> +:ref:`cs_append_ca_from_der` or :ref:`cs_append_ca_from_pem`.
> +
> .. _code_signing_consumers:
>
> Code Signing Consumers
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-06-26 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 16:08 [ptxdist] [PATCH 1/2] doc: ref_code_signing_helpers: clarify CA keyring function usage Bastian Krause
2020-06-24 16:08 ` [ptxdist] [PATCH 2/2] doc: dev_code_signing: add "Managing Certificate Authority Keyrings" Bastian Krause
2020-06-26 11:00 ` Michael Olbrich [this message]
2020-06-26 11:00 ` [ptxdist] [APPLIED] doc: ref_code_signing_helpers: clarify CA keyring function usage 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=E1jom6J-0006N9-1C@dude02.hi.pengutronix.de \
--to=mol@pengutronix.de \
--cc=bst@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
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