public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
	cip-dev@lists.cip-project.org
Subject: Re: [cip-dev][isar-cip-core][RFC v2 3/6] encrypt-data.yml: Add factory-reset information to encrypt-data
Date: Thu, 8 May 2025 14:53:12 +0200	[thread overview]
Message-ID: <fbd38d82-8a05-4fd0-afd0-e67847731f87@siemens.com> (raw)
In-Reply-To: <20250506120807.255675-4-Quirin.Gylstorff@siemens.com>

On 06.05.25 14:07, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> 
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
>  kas/opt/encrypt-data.yml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/kas/opt/encrypt-data.yml b/kas/opt/encrypt-data.yml
> index 3de76ab..4292d4c 100644
> --- a/kas/opt/encrypt-data.yml
> +++ b/kas/opt/encrypt-data.yml
> @@ -15,3 +15,6 @@ header:
>  local_conf_header:
>    initramfs-option-encrypt-partitions: |
>      OVERRIDES .= ":encrypt-partitions"
> +  initramfs-factory-reset: |
> +    INITRAMFS_FACTORY_RESET_MARKER_STORAGE_DEVICE = "/dev/disk/by-partlabel/BOOT0"
> +

Hmm, can't we probe for a reset script on all overlay devices? Then this
would be one variable less to maintain.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center


  reply	other threads:[~2025-05-08 12:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 12:07 [cip-dev][isar-cip-core][RFC v2 0/6] Add factory-reset Quirin Gylstorff
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 1/6] add factory-reset initramfs hook Quirin Gylstorff
2025-05-07  8:10   ` [cip-dev][isar-cip-core][PATCH v3 " Quirin Gylstorff
2025-05-08 12:50     ` Jan Kiszka
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 2/6] add factory-reset-helper to set the marker file Quirin Gylstorff
2025-05-08 12:51   ` Jan Kiszka
2025-05-09  8:01     ` Quirin Gylstorff
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 3/6] encrypt-data.yml: Add factory-reset information to encrypt-data Quirin Gylstorff
2025-05-08 12:53   ` Jan Kiszka [this message]
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 4/6] cip-core-image: add factory-reset helper Quirin Gylstorff
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 5/6] add factory-reset to initramfs Quirin Gylstorff
2025-05-06 12:07 ` [cip-dev][isar-cip-core][RFC v2 6/6] Add settings for factory-reset with a separate home partition Quirin Gylstorff
2025-05-15 13:12 ` [cip-dev][isar-cip-core][RFC v2 0/6] Add factory-reset Quirin Gylstorff
2025-05-15 16:37   ` 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=fbd38d82-8a05-4fd0-afd0-e67847731f87@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Quirin.Gylstorff@siemens.com \
    --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