All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai.Sathujoda@toshiba-tsip.com
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Cc: Sai <Sai.Sathujoda@toshiba-tsip.com>,
	dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: [isar-cip-core 1/3] Kconfig: Opt additional IEC 62443-4-2 features when security option is selected
Date: Wed, 30 Aug 2023 10:11:13 +0530	[thread overview]
Message-ID: <20230830044115.1112349-2-Sai.Sathujoda@toshiba-tsip.com> (raw)
In-Reply-To: <20230830044115.1112349-1-Sai.Sathujoda@toshiba-tsip.com>

From: Sai <Sai.Sathujoda@toshiba-tsip.com>

Data encryption, Secureboot and Swupdate options will be automatically
selected when security extensions is selected.

Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com>
---
 Kconfig | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Kconfig b/Kconfig
index ec49631..75d6ba4 100644
--- a/Kconfig
+++ b/Kconfig
@@ -170,6 +170,9 @@ config KAS_INCLUDE_IMAGE_FORMAT
 
 config IMAGE_SECURITY
 	bool "Security extensions"
+        select IMAGE_DATA_ENCRYPTION
+        help
+          This enables security, encrpytion, secureboot and swupdate for IEC 62443-4-2.
 
 config KAS_INCLUDE_SECURITY
 	string
-- 
2.30.2




  reply	other threads:[~2023-08-30  4:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  4:41 [isar-cip-core 0/3] Enabling additional features in security image Sai.Sathujoda
2023-08-30  4:41 ` Sai.Sathujoda [this message]
2023-08-30  4:41 ` [isar-cip-core 2/3] deploy-cip-core.sh: Workaround to search for swupdate initrd image name Sai.Sathujoda
2023-08-30  6:39   ` Jan Kiszka
2023-08-30  4:41 ` [isar-cip-core 3/3] security.yml: Add additional features to security image Sai.Sathujoda
2023-09-06  4:56 [isar-cip-core 0/3] Enabling additional features in " Sai.Sathujoda
2023-09-06  4:56 ` [isar-cip-core 1/3] Kconfig: Opt additional IEC 62443-4-2 features when security option is selected Sai.Sathujoda

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=20230830044115.1112349-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=jan.kiszka@siemens.com \
    --cc=kazuhiro3.hayashi@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.