mbox series

[0/5] Structure module signing dependencies and providers

Message ID 20250415122204.120360-1-gokhan.cetin@siemens.com
Headers show
Series Structure module signing dependencies and providers | expand

Message

Gokhan Cetin April 15, 2025, 12:21 p.m. UTC 
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          | 12 +++++++++---
 4 files changed, 22 insertions(+), 3 deletions(-)