From: Sai.Sathujoda@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, nobuhiro1.iwamatsu@toshiba.co.jp
Cc: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [cip-kernel-config 2/2] 6.1.y-cip/arm/qemu_arm_defconfig: Enable TPM-based LUKS partitions
Date: Fri, 8 Sep 2023 17:41:52 +0530 [thread overview]
Message-ID: <20230908121152.502670-2-Sai.Sathujoda@toshiba-tsip.com> (raw)
In-Reply-To: <20230908121152.502670-1-Sai.Sathujoda@toshiba-tsip.com>
From: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>
These configs allow to use LUKS encrypted partitions with
the passphrase stored in TPM2.
Signed-off-by: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>
---
6.1.y-cip/arm/qemu_arm_defconfig | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/6.1.y-cip/arm/qemu_arm_defconfig b/6.1.y-cip/arm/qemu_arm_defconfig
index 811978a..eb8cedc 100644
--- a/6.1.y-cip/arm/qemu_arm_defconfig
+++ b/6.1.y-cip/arm/qemu_arm_defconfig
@@ -186,3 +186,17 @@ CONFIG_DETECT_HUNG_TASK=y
# CONFIG_RCU_TRACE is not set
CONFIG_FUNCTION_TRACER=y
CONFIG_DEBUG_USER=y
+CONFIG_CRYPTO_HMAC=y
+CONFIG_ARM_CRYPTO=y
+CONFIG_CRYPTO_SHA256_ARM=y
+CONFIG_CRYPTO_SHA256=y
+CONFIG_CRYPTO_DRBG_MENU=y
+CONFIG_CRYPTO_DRBG_HMAC=y
+CONFIG_CRYPTO_LIB_SHA256=y
+CONFIG_CRYPTO_XTS=y
+CONFIG_CRYPTO_AES=y
+CONFIG_SECURITYFS=y
+CONFIG_TCG_TPM=y
+CONFIG_TCG_TIS_CORE=y
+CONFIG_TCG_TIS=y
+CONFIG_TCG_TIS_SPI=y
--
2.30.2
next prev parent reply other threads:[~2023-09-08 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 12:11 [cip-kernel-config 1/2] 6.1.y-cip/arm64/qemu_arm64_defconfig: Enable TPM-based LUKS partitions Sai.Sathujoda
2023-09-08 12:11 ` Sai.Sathujoda [this message]
2023-09-19 12:11 ` [cip-kernel-config 2/2] 6.1.y-cip/arm/qemu_arm_defconfig: " nobuhiro1.iwamatsu
2023-09-19 12:12 ` [cip-kernel-config 1/2] 6.1.y-cip/arm64/qemu_arm64_defconfig: " nobuhiro1.iwamatsu
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=20230908121152.502670-2-Sai.Sathujoda@toshiba-tsip.com \
--to=sai.sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.