OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/tfm_integration/psa_crypto/CMakeLists.txt

30 lines
972 B
CMake
Raw Normal View History

samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
# SPDX-License-Identifier: Apache-2.0
cmake: increase minimal required version to 3.20.0 Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-08-10 20:44:56 +08:00
cmake_minimum_required(VERSION 3.20.0)
samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
samples: make find_package(Zephyr...) REQUIRED This provides a better error message when building with CMake and forgetting ZEPHYR_BASE or not registering Zephyr in the CMake package registry. See parent commit for more details (split from parent for better readability). Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 12:02:17 +08:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
samples: psa_crypto: Create Certificate Signing Request This is a first step towards demonstrating provisioning of X.509 certificates. The device certificate signing request is created using Mbed TLS X.509 APIs. The elliptic curve key `SECP256R1` used to sign the CSR is generated inside TF-M and Mbed TLS is configured to use TF-M for crypto services. This approach will ensure that private key never leaves secure side. The CSR is encoded in JSON and is printed on the console. Signed-off-by: Devaraj Ranganna <devaraj.ranganna@linaro.org>
2021-11-08 18:16:08 +08:00
project(tfm_psa_crypto)
samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
# Source files in this sample
target_sources(app PRIVATE src/main.c)
target_sources(app PRIVATE src/psa_attestation.c)
target_sources(app PRIVATE src/psa_crypto.c)
target_sources(app PRIVATE src/shell.c)
target_sources(app PRIVATE src/util_app_cfg.c)
target_sources(app PRIVATE src/util_app_log.c)
target_sources(app PRIVATE src/util_sformat.c)
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-09 05:40:07 +08:00
target_include_directories(app PRIVATE
modules: trusted-firmware-m: Use TF-M install headers as interface Use the set of headers that the TF-M build system places in the install output. Not all public header files are available in the interface/include directory and the TF-M build system uses the install mechanism of cmake to include additional headers based on platform or configuration. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2021-11-22 23:53:04 +08:00
$<TARGET_PROPERTY:tfm,TFM_BINARY_DIR>/install/interface/include
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-09 05:40:07 +08:00
)
samples: tfm_integration: Extend PSA cryptography demo This commit extends the psa_level_1 sample's use of the PSA Cryptography 1.0 API to demonstrate the following functionality: - Generate a persistent key (secp256r1) - Display the public key based on the private key above - Calculates the SHA256 hash of a payload - Signs the hash with the persistent key - Verifies the signature using the public key - Destroys the key Signed-off-by: Kevin Townsend <kevin.townsend@linaro.org>
2020-05-14 02:03:30 +08:00
# In TF-M, default value of CRYPTO_ENGINE_BUF_SIZE is 0x2080. It causes
# insufficient memory failure while verifying signature. Increase it to 0x2400.
set_property(TARGET zephyr_property_target
APPEND PROPERTY TFM_CMAKE_OPTIONS
-DCRYPTO_ENGINE_BUF_SIZE=0x2400
)
samples: psa_crypto: Create Certificate Signing Request This is a first step towards demonstrating provisioning of X.509 certificates. The device certificate signing request is created using Mbed TLS X.509 APIs. The elliptic curve key `SECP256R1` used to sign the CSR is generated inside TF-M and Mbed TLS is configured to use TF-M for crypto services. This approach will ensure that private key never leaves secure side. The CSR is encoded in JSON and is printed on the console. Signed-off-by: Devaraj Ranganna <devaraj.ranganna@linaro.org>
2021-11-08 18:16:08 +08:00
zephyr_include_directories(${APPLICATION_SOURCE_DIR}/src/tls_config)