From: Bastian Krause <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: [ptxdist] [PATCH v2 0/5] Add code-signing-provider template, add code signing docs
Date: Fri, 12 Jun 2020 12:52:26 +0200 [thread overview]
Message-ID: <20200612105231.4318-1-bst@pengutronix.de> (raw)
The code signing infrastructure is available since 2019 in PTXdist. Now
it's time to document it, especially since RAUC also uses it.
Unfortunately this did not make it into ptxdist-2020.06.0.
To make things easier introduce a code-signing-provider template.
Changes since (implicit) v1:
- rebased on master
- reference code signing consumers section in ref_code_signing_helpers
- split into sections: {SoftHSM Provider,Generic Provider,Consumer} Functions
- add introductory sentence for each section
- added Reviewed-by Roland
- added Tested-by Ladis
Bastian Krause (5):
package templates: add code-signing-provider template
doc: dev_manual: split up into multiple files
doc: move code signing docs from scripts/ into doc/
doc: dev_code_signing: rework and extend code signing section
doc: introduce ref_code_signing_helpers
doc/dev_add_bin_only_files.rst | 105 +
doc/dev_add_new_pkgs.rst | 1339 +++++++++++++
doc/dev_code_signing.rst | 131 ++
doc/dev_create_new_pkg_templates.rst | 77 +
doc/dev_dir_hierarchy.rst | 108 +
doc/dev_layers_in_ptxdist.rst | 111 ++
doc/dev_manual.rst | 1765 +----------------
doc/ref_code_signing_helpers.rst | 264 +++
doc/ref_manual.rst | 1 +
.../code-signing-provider/ptxdist-set-keys.sh | 96 +
.../template-code-signing-provider-choice-in | 5 +
.../template-code-signing-provider-in | 16 +
.../template-code-signing-provider-make | 41 +
scripts/lib/ptxd_lib_code_signing.sh | 32 +-
scripts/lib/ptxd_lib_template.sh | 16 +
15 files changed, 2322 insertions(+), 1785 deletions(-)
create mode 100644 doc/dev_add_bin_only_files.rst
create mode 100644 doc/dev_add_new_pkgs.rst
create mode 100644 doc/dev_code_signing.rst
create mode 100644 doc/dev_create_new_pkg_templates.rst
create mode 100644 doc/dev_dir_hierarchy.rst
create mode 100644 doc/dev_layers_in_ptxdist.rst
create mode 100644 doc/ref_code_signing_helpers.rst
create mode 100755 rules/templates/code-signing-provider/ptxdist-set-keys.sh
create mode 100644 rules/templates/template-code-signing-provider-choice-in
create mode 100644 rules/templates/template-code-signing-provider-in
create mode 100644 rules/templates/template-code-signing-provider-make
--
2.27.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2020-06-12 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 10:52 Bastian Krause [this message]
2020-06-12 10:52 ` [ptxdist] [PATCH v2 1/5] package templates: add code-signing-provider template Bastian Krause
2020-06-12 10:56 ` Bastian Krause
2020-06-12 10:52 ` [ptxdist] [PATCH v2 2/5] doc: dev_manual: split up into multiple files Bastian Krause
2020-06-12 10:52 ` [ptxdist] [PATCH v2 3/5] doc: move code signing docs from scripts/ into doc/ Bastian Krause
2020-06-12 10:52 ` [ptxdist] [PATCH v2 4/5] doc: dev_code_signing: rework and extend code signing section Bastian Krause
2020-06-12 10:52 ` [ptxdist] [PATCH v2 5/5] doc: introduce ref_code_signing_helpers Bastian Krause
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=20200612105231.4318-1-bst@pengutronix.de \
--to=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