From: "'Kumar, Rakesh' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>
Cc: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
Subject: RE: [PATCH] initramfs: move fTPM and tee-supplicant initialization to local-top stage
Date: Mon, 22 Jul 2024 05:43:54 +0000 [thread overview]
Message-ID: <SG2PR06MB5189A49EE62C2C306267649297A82@SG2PR06MB5189.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <fa89edf3-30be-4692-baa1-9c69876c96d4@siemens.com>
Hi all,
Any updates on this patch.
If this patch needs any correction/improvement then please give your inputs on this.
Regards,
Rakesh
-----Original Message-----
From: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
Sent: 10 July 2024 16:51
To: Kumar, Rakesh (DI CTO FDS CES LX PBU 1) <kumar.rakesh@siemens.com>; isar-users@googlegroups.com; Gylstorff, Quirin (T CED OES-DE) <quirin.gylstorff@siemens.com>
Cc: Hombourger, Cedric (DI CTO FDS CES LX) <cedric.hombourger@siemens.com>
Subject: Re: [PATCH] initramfs: move fTPM and tee-supplicant initialization to local-top stage
On 10.07.24 07:33, Rakesh Kumar wrote:
> To ensure proper initialization of the fTPM and tee-supplicant
> services before the root filesystem is mounted, we are relocating
> their initialization to the local-top section of initramfs. This
> change ensures that the encrypted filesystems are properly initialized
> and ready for use before the root filesystem is mounted at local-bottom stage.
Close but not fully correct: The rootfs is mounted AFTER the top stage and BEFORE bottom.
>
> Reason for local-top:
>
> * Early Initialization: The local-top scripts run before the root filesystem is mounted.
> This timing is essential for encrypted root filesystems since the decryption process must be
> completed before the filesystem can be accessed.
>
> * Dependency Handling: The encryption setup requires initializing dependencies such as
> fTPM (firmware Trusted Platform Module) devices. Performing these tasks early in the boot process
> ensures that all necessary components are in place before the root filesystem is mounted.
This will still need some isar-cip-core patch in order to add a PREREQ on fTPM if a concrete target using fTPM for disk encryption. But Quirin just had another idea, leaving the stage to him now. :)
Jan
>
> Signed-off-by: Rakesh Kumar <kumar.rakesh@siemens.com>
> ---
> .../initramfs-tee-ftpm-hook/initramfs-tee-ftpm-hook_0.1.bb | 4 ++--
> .../initramfs-tee-supplicant-hook_0.1.bb | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
> a/meta/recipes-initramfs/initramfs-tee-ftpm-hook/initramfs-tee-ftpm-ho
> ok_0.1.bb
> b/meta/recipes-initramfs/initramfs-tee-ftpm-hook/initramfs-tee-ftpm-ho
> ok_0.1.bb
> index db38e618..82fec1bb 100644
> ---
> a/meta/recipes-initramfs/initramfs-tee-ftpm-hook/initramfs-tee-ftpm-ho
> ok_0.1.bb
> +++ b/meta/recipes-initramfs/initramfs-tee-ftpm-hook/initramfs-tee-ftp
> +++ m-hook_0.1.bb
> @@ -17,11 +17,11 @@ DEBIAN_DEPENDS = "initramfs-tools"
>
> do_install[cleandirs] += " \
> ${D}/usr/share/initramfs-tools/hooks \
> - ${D}/usr/share/initramfs-tools/scripts/local-bottom"
> + ${D}/usr/share/initramfs-tools/scripts/local-top"
>
> do_install() {
> install -m 0755 "${WORKDIR}/tee-ftpm.hook" \
> "${D}/usr/share/initramfs-tools/hooks/tee-ftpm"
> install -m 0755 "${WORKDIR}/tee-ftpm.script" \
> - "${D}/usr/share/initramfs-tools/scripts/local-bottom/tee-ftpm"
> + "${D}/usr/share/initramfs-tools/scripts/local-top/tee-ftpm"
> }
> diff --git
> a/meta/recipes-initramfs/initramfs-tee-supplicant-hook/initramfs-tee-s
> upplicant-hook_0.1.bb
> b/meta/recipes-initramfs/initramfs-tee-supplicant-hook/initramfs-tee-s
> upplicant-hook_0.1.bb
> index 3768b8e0..a7a19bee 100644
> ---
> a/meta/recipes-initramfs/initramfs-tee-supplicant-hook/initramfs-tee-s
> upplicant-hook_0.1.bb
> +++ b/meta/recipes-initramfs/initramfs-tee-supplicant-hook/initramfs-t
> +++ ee-supplicant-hook_0.1.bb
> @@ -17,11 +17,11 @@ DEBIAN_DEPENDS = "initramfs-tools, tee-supplicant, procps"
>
> do_install[cleandirs] += " \
> ${D}/usr/share/initramfs-tools/hooks \
> - ${D}/usr/share/initramfs-tools/scripts/local-bottom"
> + ${D}/usr/share/initramfs-tools/scripts/local-top"
>
> do_install() {
> install -m 0755 "${WORKDIR}/tee-supplicant.hook" \
> "${D}/usr/share/initramfs-tools/hooks/tee-supplicant"
> install -m 0755 "${WORKDIR}/tee-supplicant.script" \
> - "${D}/usr/share/initramfs-tools/scripts/local-bottom/tee-supplicant"
> + "${D}/usr/share/initramfs-tools/scripts/local-top/tee-supplicant"
> }
--
Siemens AG, Technology
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 on the web visit https://groups.google.com/d/msgid/isar-users/SG2PR06MB5189A49EE62C2C306267649297A82%40SG2PR06MB5189.apcprd06.prod.outlook.com.
next prev parent reply other threads:[~2024-07-22 5:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 5:33 'Rakesh Kumar' via isar-users
2024-07-10 11:21 ` 'Jan Kiszka' via isar-users
2024-07-10 12:30 ` 'Rakesh Kumar' via isar-users
2024-07-10 12:39 ` Rakesh Kumar
2024-07-13 14:55 ` Rakesh Kumar
2024-07-22 5:43 ` 'Kumar, Rakesh' via isar-users [this message]
2024-07-22 8:52 ` Uladzimir Bely
2024-07-22 13:31 ` Rakesh Kumar
2024-07-23 7:37 ` Uladzimir Bely
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=SG2PR06MB5189A49EE62C2C306267649297A82@SG2PR06MB5189.apcprd06.prod.outlook.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kumar.rakesh@siemens.com \
--cc=quirin.gylstorff@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