public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Gokhan Cetin <gokhan.cetin@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 5/5] doc/user_manual: describe module signer and certificate provider configuration
Date: Tue, 15 Apr 2025 17:26:31 +0200	[thread overview]
Message-ID: <f384d67d-e7fa-4308-8a96-4f85e6760bc5@siemens.com> (raw)
In-Reply-To: <20250415122204.120360-6-gokhan.cetin@siemens.com>

On 15.04.25 14:22, 'Gokhan Cetin' via isar-users wrote:
> Mentions how `SIGNATURE_ENABLED` can be used and how to manage the dependencies.
> 
> Signed-off-by: Gokhan Cetin <gokhan.cetin@siemens.com>
> ---
>  doc/user_manual.md | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index d8e5c33e..50d98f85 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -1162,9 +1162,17 @@ To provide a signer script that implements your custom signing solution, `SIGNAT
>  can be set for the script path within the module recipe together with `SIGNATURE_CERTFILE` to define the public
>  certificate path of the signer.
>  
> +In order to easily choose between different signing solutions, signer recipes should provide the `module-signer`

...target and package

> +and certificate provider recipes should provide the `secure-boot-secrets` as virtual package to meet build dependencies.
> +This way, desired signers and certificates can be configured using `PREFERRED_PROVIDER`.
> +
>  Please see how `module-signer-example` hook generates a detached signature for the kernel module implemented in
>  `example-module-signedwith` recipe.
>  
> +In order not to cause repetitive changes in kernel module recipes, 

I think this argument need not be in the user manual. It's enough to
state that there is variable to enable signing (per recipe or globally,
see patch 4).

> +if `SIGNATURE_ENABLED = "1"`, `pkg.signwith` build profile is added by default in addition to
> +`module-signer` and `secure-boot-secrets` package dependencies to the kernel module recipes.
> +
>  ### Cross Support for Imagers
>  
>  If `ISAR_CROSS_COMPILE = "1"`, the imager and optional compression tasks

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f384d67d-e7fa-4308-8a96-4f85e6760bc5%40siemens.com.

      reply	other threads:[~2025-04-15 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 12:21 [PATCH 0/5] Structure module signing dependencies and providers 'Gokhan Cetin' via isar-users
2025-04-15 12:22 ` [PATCH 1/5] module-signer-example: define virtual package name as module-signer 'Gokhan Cetin' via isar-users
2025-04-15 12:22 ` [PATCH 2/5] meta/recipes-kernel/linux-module: Define default paths for signing related variables 'Gokhan Cetin' via isar-users
2025-04-15 12:22 ` [PATCH 3/5] meta-isar/recipes-secureboot/sb-mok-keys: define virtual package name 'Gokhan Cetin' via isar-users
2025-04-15 12:22 ` [PATCH 4/5] meta/recipes-kernel/linux-module: add option to set default signing profile and dependencies 'Gokhan Cetin' via isar-users
2025-04-15 15:25   ` 'Jan Kiszka' via isar-users
2025-04-15 12:22 ` [PATCH 5/5] doc/user_manual: describe module signer and certificate provider configuration 'Gokhan Cetin' via isar-users
2025-04-15 15:26   ` 'Jan Kiszka' via isar-users [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=f384d67d-e7fa-4308-8a96-4f85e6760bc5@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=gokhan.cetin@siemens.com \
    --cc=jan.kiszka@siemens.com \
    /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