mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: rhi@pengutronix.de, Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 0/5] Add code-signing-provider template, add code signing docs
Date: Fri, 12 Jun 2020 12:04:00 +0200	[thread overview]
Message-ID: <20200612100400.GE27654@pengutronix.de> (raw)
In-Reply-To: <20200608085305.30964-1-bst@pengutronix.de>

On Mon, Jun 08, 2020 at 10:53:00AM +0200, Bastian Krause wrote:
> 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.

This looks already quite nice. Thank you. Other than the comments I've made
for some of the patches, this is good to merge.

Michael

> 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                      |  129 ++
>  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.inc              |  246 +++
>  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, 2302 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.inc
>  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
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

      parent reply	other threads:[~2020-06-12 10:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  8:53 Bastian Krause
2020-06-08  8:53 ` [ptxdist] [PATCH 1/5] package templates: add code-signing-provider template Bastian Krause
2020-06-12  9:18   ` Michael Olbrich
2020-06-12  9:54     ` Michael Olbrich
2020-06-12 10:05       ` Michael Olbrich
2020-06-12 11:05         ` Bastian Krause
2020-06-17 14:45           ` Bastian Krause
2020-06-16 13:56     ` Bastian Krause
2020-06-16 15:00       ` Michael Olbrich
2020-06-08  8:53 ` [ptxdist] [PATCH 2/5] doc: dev_manual: split up into multiple files Bastian Krause
2020-06-08  8:53 ` [ptxdist] [PATCH 3/5] doc: move code signing docs from scripts/ into doc/ Bastian Krause
2020-06-08  8:53 ` [ptxdist] [PATCH 4/5] doc: dev_code_signing: rework and extend code signing section Bastian Krause
2020-06-08 10:16   ` Roland Hieber
2020-06-12  8:55     ` Bastian Krause
2020-06-08  8:53 ` [ptxdist] [PATCH 5/5] doc: introduce ref_code_signing_helpers Bastian Krause
2020-06-12  9:28   ` Michael Olbrich
2020-06-12  9:49   ` Michael Olbrich
2020-06-08 10:17 ` [ptxdist] [PATCH 0/5] Add code-signing-provider template, add code signing docs Roland Hieber
2020-06-09 15:04   ` Ladislav Michl
2020-06-12 10:04 ` 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:
  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=20200612100400.GE27654@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=bst@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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