public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Gokhan Cetin' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: gokhan.cetin@siemens.com, jan.kiszka@siemens.com
Subject: [PATCH v2 0/5] Structure module signing dependencies and providers
Date: Wed, 16 Apr 2025 19:17:04 +0200	[thread overview]
Message-ID: <20250416171709.742191-1-gokhan.cetin@siemens.com> (raw)

As of now, in each kernel module, the same configuration block
has to be specified repeatedly for each module in module recipes
to specify build-time dependencies on recipes that provide the
required build profile and the scripts and certificates used in 
kernel module signing.

With these changes, it is possible to enable a recommended signature
configuration for all module recipes without touching the modules,
while it is still possible to customize the configuration when necessary.

Gokhan Cetin (5):
  module-signer-example: define virtual package name as module-signer
  meta/recipes-kernel/linux-module: Define default paths for signing
    related variables
  meta-isar/recipes-secureboot/sb-mok-keys: define virtual package name
  meta/recipes-kernel/linux-module: add option to set default signing
    profile and dependencies
  doc/user_manual: describe module signer and certificate provider
    configuration

 doc/user_manual.md                                  |  8 ++++++++
 .../module-signer-example/module-signer-example.bb  |  3 +++
 .../recipes-secureboot/sb-mok-keys/sb-mok-keys.bb   |  2 ++
 meta/recipes-kernel/linux-module/module.inc         | 13 ++++++++++---
 4 files changed, 23 insertions(+), 3 deletions(-)

-- 
2.39.2

-- 
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/20250416171709.742191-1-gokhan.cetin%40siemens.com.

             reply	other threads:[~2025-04-16 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 17:17 'Gokhan Cetin' via isar-users [this message]
2025-04-16 17:17 ` [PATCH v2 1/5] module-signer-example: define virtual package name as module-signer 'Gokhan Cetin' via isar-users
2025-04-16 17:17 ` [PATCH v2 2/5] meta/recipes-kernel/linux-module: Define default paths for signing related variables 'Gokhan Cetin' via isar-users
2025-04-16 17:17 ` [PATCH v2 3/5] meta-isar/recipes-secureboot/sb-mok-keys: define virtual package name 'Gokhan Cetin' via isar-users
2025-04-16 17:17 ` [PATCH v2 4/5] meta/recipes-kernel/linux-module: add option to set default signing profile and dependencies 'Gokhan Cetin' via isar-users
2025-04-16 17:17 ` [PATCH v2 5/5] doc/user_manual: describe module signer and certificate provider configuration 'Gokhan Cetin' 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=20250416171709.742191-1-gokhan.cetin@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