From: Jan Kiszka <jan.kiszka@siemens.com>
To: Claudius Heine <ch@denx.de>, cip-dev@lists.cip-project.org
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Alexander <alexander.heinisch@siemens.com>,
"Cetin, Gokhan" <gokhan.cetin@siemens.com>
Subject: Re: [PATCH v6 0/4] initramfs-crypt-hook patch
Date: Mon, 2 Jun 2025 10:24:54 +0200 [thread overview]
Message-ID: <a22f282c-efea-4cfd-9870-118e1950b828@siemens.com> (raw)
In-Reply-To: <DABWFSN87AVE.H2RGOY175Z6S@denx.de>
On 02.06.25 10:20, Claudius Heine wrote:
> On Fri May 30, 2025 at 4:19 PM CEST, Jan Kiszka wrote:
>> On 20.03.25 08:43, Claudius Heine wrote:
>>> Hi,
>>>
>>> here is v6 of my patchset.
>>>
>>> I fixed the issue I found in the last patchset, now the `format-if-empty` process is a bit more power-fail save.
>>>
>>> But I suppose that if the luks header could not be written fully, and the `luks` fs type is not detected, it might still cause issues, but I am not sure I can prevent that effectively.
>>>
>>> Kind regards,
>>> Claudius
>>>
>>> ---
>>> Changes in v6:
>>> - luks formatting of format-if-empty will now be redone when if it is a
>>> luks partition without a TPM2 token, this makes it a bit more
>>> power-fail save
>>> - Link to v5: https://lore.kernel.org/r/20250313-initramfs-crypt-hook-patches-2-v5-0-fc62d4a2ad29@denx.de
>>>
>>> Changes in v5:
>>> - Switch to use TPM2 protected password instead of static initial
>>> password for encryption
>>> - Link to v4: https://lore.kernel.org/r/20250305-initramfs-crypt-hook-patches-2-v4-0-4170912e5261@denx.de
>>>
>>> Changes in v4:
>>> - improve documentation and commit messages
>>> - reorder commits, to put re-encryption recovery up front
>>> - extract static temporary encryption key patch into its own
>>> - switch from lsblk to blkid
>>>
>>> Changes in v3:
>>> - Rebase on current next
>>> - Extended `noencrypt` documentation
>>> - support clevis tokens for re-encryption recovery
>>>
>>> Changes in v2:
>>> - Added more descriptive commit message
>>> - Added more descriptive documentation about noencrypt option
>>> - Fixed typos in documentation
>>> - removed unnecessary setting of /conf/param.conf in initramfs-crypt-hook
>>> - added re-encryption recovery patch
>>>
>>> ---
>>> Claudius Heine (4):
>>> initramfs-crypt-hook: store initial encryption key in TPM2
>>> initramfs-crypt-hook: add re-encryption recovery
>>> initramfs-crypt-hook: implement 'noencrypt' option
>>> initramfs-crypt-hook: add 'format-if-empty' feature
>>>
>>> doc/README.tpm2.encryption.md | 25 +++-
>>> .../initramfs-crypt-hook/files/local-top-complete | 127 +++++++++++++++++++--
>>> .../initramfs-crypt-hook_0.7.bb | 12 +-
>>> 3 files changed, 146 insertions(+), 18 deletions(-)
>>> ---
>>> base-commit: f5661b18b9721eee984ffc3b75169b40508469cb
>>> change-id: 20250305-initramfs-crypt-hook-patches-2-9cc4a027c89a
>>>
>>> Best regards,
>>
>> Seems this got lost after 1.7, Gökhan just reminded me. Any updates for
>> this in the meantime?
>
> From my side v6 is still awaiting review. You mentioned that you will
> not merge it now, but in the future, and I have not received any further
> comments about this code so far.
OK, then everyone in CC should please have a look now and provide
feedback. The good news is that it still applies cleanly.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-06-02 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 7:43 [PATCH v6 0/4] initramfs-crypt-hook patch Claudius Heine
2025-03-20 7:43 ` [PATCH v6 1/4] initramfs-crypt-hook: store initial encryption key in TPM2 Claudius Heine
2025-03-20 7:43 ` [PATCH v6 2/4] initramfs-crypt-hook: add re-encryption recovery Claudius Heine
2025-03-20 7:43 ` [PATCH v6 3/4] initramfs-crypt-hook: implement 'noencrypt' option Claudius Heine
2025-03-20 7:43 ` [PATCH v6 4/4] initramfs-crypt-hook: add 'format-if-empty' feature Claudius Heine
2025-05-30 14:19 ` [PATCH v6 0/4] initramfs-crypt-hook patch Jan Kiszka
2025-06-02 8:20 ` Claudius Heine
2025-06-02 8:24 ` Jan Kiszka [this message]
2025-06-11 20:46 ` Cetin, Gokhan
2025-06-16 9:35 ` Claudius Heine
2025-06-16 11:11 ` Jan Kiszka
2025-06-16 11:58 ` Jan Kiszka
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=a22f282c-efea-4cfd-9870-118e1950b828@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alexander.heinisch@siemens.com \
--cc=ch@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=gokhan.cetin@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