From: yuecelm@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: signing support for (in-tree and external) kernel modules
Date: Wed, 29 Apr 2020 06:00:58 -0700 (PDT) [thread overview]
Message-ID: <9a590808-34da-493f-9ea2-219d17cd87c9@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]
In tree kernel modules gets signed with the CONFIG_MODULE_SIG_ALL kernel
option, but extra (resp. external) modules not. If you (resp. isar) not
provide an (external) signing key, the kernel build autogenerates a
private/public key pair. It would be nice if the isar build system provide
some support for signing kernel modules.
I see currently 2 use cases:
1) let the kernel build to autogenerate private/public key for kernel
module signing and kernel-module reuse the key for signing (evt. isar
deletes the private key after image generation)
2) provide an (external) private and public key for kernel module signing
and will be used in kernel and kernel-module recipes
[-- Attachment #1.2: Type: text/html, Size: 772 bytes --]
next reply other threads:[~2020-04-29 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 13:00 yuecelm [this message]
2020-04-29 15:35 ` Jan Kiszka
2020-04-29 16:51 ` Mustafa Yücel
2020-04-29 17:38 ` Jan Kiszka
2020-04-29 18:57 ` Mustafa Yücel
2020-04-29 20:15 ` Henning Schild
2020-04-29 21:04 ` Mustafa Yücel
2020-04-30 10:42 ` Henning Schild
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=9a590808-34da-493f-9ea2-219d17cd87c9@googlegroups.com \
--to=yuecelm@gmail.com \
--cc=isar-users@googlegroups.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