public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH 0/5] Initramfs-crypt-hook patches, encryption on update
Date: Wed, 26 Feb 2025 10:59:16 +0100	[thread overview]
Message-ID: <20250226095921.168962-1-ch@denx.de> (raw)

Hi,

I have a couple patches for initramfs-crypt-hook scripts. The first
three are general fixes/cleanup patches and the last two are about
enabling support for encryption via and update, while not touching the
fallback system.

I also have a patch that makes the 'reencrypt' continue, if the power
fails while it happens, but to do that, the initramfs needs to know the
temporary password that was used after a reboot, which currently does
not work with the random temporary passwords used here. My current
solution is to use a static temporary password for the reencryption
process. Any ideas?

kind regards,
Claudius

Claudius Heine (5):
  initramfs-crypt-hook: make sure that mount path exists
  initramfs-crypt-hook: fix inconsistent whitespace
  initramfs-crypt-hook: use real device path in luksFormat case
  initramfs-crypt-hook: implement 'noencrypt' option
  initramfs-crypt-hook: add 'format-if-empty' feature

 doc/README.tpm2.encryption.md                 |  4 +-
 .../files/local-bottom-complete               |  1 +
 .../files/local-top-complete                  | 49 ++++++++++++++++---
 .../initramfs-crypt-hook_0.6.bb               |  2 +-
 4 files changed, 47 insertions(+), 9 deletions(-)

-- 
2.39.5



             reply	other threads:[~2025-02-26  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26  9:59 Claudius Heine [this message]
2025-02-26  9:59 ` [PATCH 1/5] initramfs-crypt-hook: make sure that mount path exists Claudius Heine
2025-02-27  9:13   ` Jan Kiszka
2025-02-26  9:59 ` [PATCH 2/5] initramfs-crypt-hook: fix inconsistent whitespace Claudius Heine
2025-02-27  9:14   ` Jan Kiszka
2025-02-26  9:59 ` [PATCH 3/5] initramfs-crypt-hook: use real device path in luksFormat case Claudius Heine
2025-02-27  9:16   ` Jan Kiszka
2025-02-27 12:47     ` Quirin Gylstorff
2025-02-27 12:49   ` Jan Kiszka
2025-02-26  9:59 ` [PATCH 4/5] initramfs-crypt-hook: implement 'noencrypt' option Claudius Heine
2025-02-27  9:17   ` Jan Kiszka
2025-02-27  9:55     ` Claudius Heine
2025-02-27 12:48       ` Jan Kiszka
2025-02-27 13:16   ` [cip-dev] " Quirin Gylstorff
2025-02-27 14:04     ` Claudius Heine
2025-02-26  9:59 ` [PATCH 5/5] initramfs-crypt-hook: add 'format-if-empty' feature Claudius Heine

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=20250226095921.168962-1-ch@denx.de \
    --to=ch@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    /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