5888428541
Introducing MBEDTLS_PROMPTLESS and CUSTOM_MBEDTLS_CFG_FILE settings. The MBEDTLS_PROMPTLESS can be set to true whenever configuration of mbedTLS is done from a subsystem or module. Such an example is OpenThread, which selects mbedTLS for some predefined crypto settings using OPENTHREAD_MBEDTLS=y. Unfortunately, extensive use of select can easily cause stuck symbol syndrome making it harder than neccesarry for users to later reconfigure as they easily get stuck in incompatible configurations. Providing a MBEDTLS_PROMPTLESS allows such configurations to disable the MBEDTLS prompt itself when selected but avoid stuck symbol if user select another security configuration. Similar with CUSTOM_MBEDTLS_CFG_FILE which ensures that user must explicitly select this symbol before providing a custom mbedTLS config file. Today, other parts the Kconfig tree may set a default value for MBEDTLS_CFG_FILE but that value is stuck and thus changed Kconfig selections elsewhere in the tree will not adjust the value. Introducing CUSTOM_MBEDTLS_CFG_FILE ensures it is known when the user has provided the value. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> |
||
---|---|---|
.. | ||
hal_nordic | ||
mbedtls | ||
nanopb | ||
segger | ||
tensorflow | ||
TraceRecorder | ||
trusted-firmware-m | ||
Kconfig | ||
Kconfig.altera | ||
Kconfig.atmel | ||
Kconfig.canopennode | ||
Kconfig.civetweb | ||
Kconfig.cmsis | ||
Kconfig.cmsis_dsp | ||
Kconfig.cypress | ||
Kconfig.eos_s3 | ||
Kconfig.imx | ||
Kconfig.infineon | ||
Kconfig.libmetal | ||
Kconfig.loramac-node | ||
Kconfig.mcuboot_bootutil | ||
Kconfig.mcux | ||
Kconfig.microchip | ||
Kconfig.nuvoton | ||
Kconfig.open-amp | ||
Kconfig.silabs | ||
Kconfig.simplelink | ||
Kconfig.sof | ||
Kconfig.st | ||
Kconfig.stm32 | ||
Kconfig.syst | ||
Kconfig.tinycbor | ||
Kconfig.tinycrypt | ||
Kconfig.vega | ||
Kconfig.xtensa | ||
modules.cmake |