summaryrefslogtreecommitdiff
path: root/lib/Kconfig
diff options
context:
space:
mode:
authorManorit Chawdhry <m-chawdhry@ti.com>2023-06-16 14:34:30 +0530
committerUdit Kumar <u-kumar1@ti.com>2023-06-19 19:20:47 +0530
commit13b330292c536a7706f4b67bda888279bb0f04a5 (patch)
tree847f4235ca24328cce3dd38b3b549c1bcf7245a7 /lib/Kconfig
parent9dc6f87640897f1323b46427baffcb3ed949c1ee (diff)
lib: Kconfig: k3: Enable SHA512 for fit signature
We are using our custMpk for signing that is a 4096 bit key, 4096 bit rsa key requires a SHA512 hashing algorithm to be enabled as per the source. Even though it is not mandated but this is how it works and is tested. Enables SHA512 if fit signature is enabled on K3 platforms. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Diffstat (limited to 'lib/Kconfig')
-rw-r--r--lib/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/Kconfig b/lib/Kconfig
index 83e5edd73b..d81a88a982 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -496,6 +496,7 @@ config SHA256
config SHA512
bool "Enable SHA512 support"
+ default y if TI_SECURE_DEVICE && FIT_SIGNATURE
help
This option enables support of hashing using SHA512 algorithm.
The hash is calculated in software.