From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Gokhan Cetin <gokhan.cetin@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 4/5] meta/recipes-kernel/linux-module: add option to set default signing profile and dependencies
Date: Tue, 15 Apr 2025 17:25:35 +0200 [thread overview]
Message-ID: <73ca026a-3f26-44c1-a2df-c305a2e2d71f@siemens.com> (raw)
In-Reply-To: <20250415122204.120360-5-gokhan.cetin@siemens.com>
On 15.04.25 14:22, 'Gokhan Cetin' via isar-users wrote:
> Introduces single configuration variable (`SIGNATURE_ENABLED`) to
> set all predefined profile and dependencies need to be provided.
>
> By using this option, downstreams will be able to sign all
> kernel modules without appending any additional configuration
> into their module recipes.
>
> Signed-off-by: Gokhan Cetin <gokhan.cetin@siemens.com>
> ---
> meta/recipes-kernel/linux-module/module.inc | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-kernel/linux-module/module.inc b/meta/recipes-kernel/linux-module/module.inc
> index 45d88d48..576a2cad 100644
> --- a/meta/recipes-kernel/linux-module/module.inc
> +++ b/meta/recipes-kernel/linux-module/module.inc
> @@ -27,6 +27,12 @@ SIGNATURE_KEYFILE ??= "/usr/share/secure-boot-secrets/secure-boot.key"
> SIGNATURE_CERTFILE ??= "/usr/share/secure-boot-secrets/secure-boot.pem"
> SIGNATURE_HASHFN ??= "sha256"
> SIGNATURE_SIGNWITH ??= "/usr/bin/sign-module.sh"
> +SIGNATURE_ENABLED ??= ""
Should this last control actually be by module recipe (which includes
module.inc), or shouldn't we also support build-wide enabling via
local.conf etc.? In the latter case, isar should introduce a global
control variable, say KERNEL_MODULE_SIGNATURES, which controls that for
every module recipe.
Jan
> +
> +# Define signing profile and dependencies if SIGNATURE_ENABLED is set to "1"
> +DEB_BUILD_PROFILES += "${@'pkg.signwith' if bb.utils.to_boolean(d.getVar('SIGNATURE_ENABLED')) else ''}"
> +DEPENDS += "${@'module-signer secure-boot-secrets' if bb.utils.to_boolean(d.getVar('SIGNATURE_ENABLED')) else ''}"
> +DEBIAN_BUILD_DEPENDS .= "${@', module-signer, secure-boot-secrets' if bb.utils.to_boolean(d.getVar('SIGNATURE_ENABLED')) else ''}"
>
> SRC_URI += "file://debian/"
>
--
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/73ca026a-3f26-44c1-a2df-c305a2e2d71f%40siemens.com.
next prev parent reply other threads:[~2025-04-15 15:25 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 [this message]
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
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=73ca026a-3f26-44c1-a2df-c305a2e2d71f@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