Searched full:psa (Results 1 – 25 of 167) sorted by relevance
1234567
/Zephyr-latest/samples/psa/persistent_key/ |
D | README.rst | 2 :name: PSA Crypto persistent key 4 Manage and use persistent keys via the PSA Crypto API. 9 This sample demonstrates usage of persistent keys in the :ref:`PSA Crypto API <psa_crypto>`. 14 In addition to the PSA Crypto API, an implementation of the 15 `PSA Internal Trusted Storage (ITS) API <https://arm-software.github.io/psa-api/storage/1.0/overvie… 25 This sample is located in :zephyr_file:`samples/psa/persistent_key`. 28 You can use them to build the sample, depending on the PSA ITS provider, as follows: 37 :zephyr-app: samples/psa/persistent_key 41 :west-args: -T sample.psa.persistent_key.tfm 50 :zephyr-app: samples/psa/persistent_key [all …]
|
D | sample.yaml | 2 name: PSA Crypto persistent key sample 3 description: Demonstration of persistent key usage in the PSA Crypto API. 6 - psa.secure_storage 14 sample.psa.persistent_key.tfm: 19 sample.psa.persistent_key.secure_storage.entropy_driver: 26 sample.psa.persistent_key.secure_storage.entropy_not_secure:
|
/Zephyr-latest/samples/psa/its/ |
D | README.rst | 2 :name: PSA Internal Trusted Storage API 5 Use the PSA ITS API. 11 `PSA Internal Trusted Storage (ITS) API <https://arm-software.github.io/psa-api/storage/1.0/overvie… 12 which is part of the `PSA Secure Storage API <https://arm-software.github.io/psa-api/storage/>`_, 18 An implementation of the PSA ITS API must be present for this sample to build. 27 This sample is located in :zephyr_file:`samples/psa/its`. 30 You can use them to build the sample, depending on the PSA ITS provider, as follows: 39 :zephyr-app: samples/psa/its 43 :west-args: -T sample.psa.its.tfm 52 :zephyr-app: samples/psa/its [all …]
|
D | sample.yaml | 2 name: PSA ITS API sample 3 description: Demonstration of PSA Internal Trusted Storage (ITS) API usage. 6 - psa.secure_storage 14 sample.psa.its.tfm: 19 sample.psa.its.secure_storage.entropy_driver: 26 sample.psa.its.secure_storage.entropy_not_secure:
|
/Zephyr-latest/samples/tfm_integration/psa_crypto/ |
D | Kconfig | 1 # Private config options for PSA Crypto application 6 mainmenu "PSA Crypto sample application" 10 module = PSA 11 module-str = psa 17 bool "The 'psa' shell command" 20 Enabling this option will make the 'psa' shell command available. 26 private key using PSA APIs and PRIVATE_KEY_STATIC or
|
/Zephyr-latest/doc/services/tfm/ |
D | testsuites.rst | 7 * psa-arch-tests - Test suites for specific PSA APIs (secure storage, etc.) 18 NS/S boundary via the PSA APIs. They provide a useful sanity check for proper 22 PSA Arch Tests 25 The PSA Arch Test suite, available via :ref:`tfm_psa_test`, contains a number of 26 test suites that can be used to validate that PSA API specifications are 28 the Platform Security Architecture (PSA). 36 The output of these test suites is required to obtain PSA Certification for 37 your specific board, RTOS (Zephyr here), and PSA implementation (TF-M in this
|
/Zephyr-latest/include/zephyr/psa/ |
D | key_ids.h | 8 * @file zephyr/psa/key_ids.h 10 * @brief This file defines the key ID ranges of the existing users of the PSA Crypto API. 13 * PSA Crypto API. Because they are not aware of each other, collisions are avoided by having them 15 * This file acts as the registry of all the allocated PSA key ID ranges within Zephyr. 20 * are chosen to be somewhere in the PSA user key ID range to try to avoid collisions 27 /** PSA key ID range to be used by OpenThread. The base ID is equal to the default value upstream: 33 /** PSA key ID range to be used by Matter. The base ID is equal to the default value upstream: 39 /** PSA key ID range to be used by Bluetooth Mesh. */ 43 /** PSA key ID range to be used by Wi-Fi credentials management. */ 47 /** PSA key ID range to be used by the end-user application. */
|
/Zephyr-latest/samples/psa/ |
D | index.rst | 1 .. zephyr:code-sample-category:: psa 2 :name: PSA 6 `Platform Security Architecture (PSA) Certified APIs <https://arm-software.github.io/psa-api/>`_.
|
/Zephyr-latest/tests/subsys/secure_storage/psa/its/ |
D | testcase.yaml | 9 - psa.secure_storage 11 secure_storage.psa.its.secure_storage.store.zms: 30 secure_storage.psa.its.secure_storage.store.settings: 35 secure_storage.psa.its.secure_storage.custom.transform: 40 secure_storage.psa.its.secure_storage.custom.store: 45 secure_storage.psa.its.secure_storage.custom.both: 50 secure_storage.psa.its.tfm:
|
/Zephyr-latest/tests/crypto/mbedtls_psa/ |
D | testcase.yaml | 1 # The goal here is to showcase that Mbed TLS's PSA crypto implementation can be 3 # enable support for PSA crypto APIs in Mbed TLS and then test them with: 4 # - psa_crypto_init() which is required before any PSA crypto operation 5 # - psa_generate_random() which is always available as long as PSA crypto is 12 # of PSA crypto is working fine on the platforms that support TF-M. 21 - psa
|
/Zephyr-latest/subsys/secure_storage/include/psa/ |
D | storage_common.h | 7 * @defgroup psa_secure_storage PSA Secure Storage API 9 * @details For more information on the PSA Secure Storage API, see the 10 * [PSA Certified Secure Storage API](https://arm-software.github.io/psa-api/storage/1.0/) 14 * @file psa/storage_common.h 16 * @brief Common definitions of the PSA Secure Storage API. 19 #include <psa/error.h>
|
/Zephyr-latest/samples/tfm_integration/psa_crypto/src/ |
D | util_app_log.h | 9 #include "psa/error.h" 10 #include "psa/initial_attestation.h" 11 #include "psa/protected_storage.h" 18 * @brief Logs PSA response messages other than PSA_SUCCESS for debugging
|
D | shell.c | 29 /* Subcommand array for "psa" (level 1). */ 37 /* Root command "psa" (level 0). */ 38 SHELL_CMD_REGISTER(psa, &sub_psa, "PSA commands", NULL);
|
D | psa_crypto.h | 9 #include "psa/crypto.h" 10 #include "psa/error.h" 22 * @brief Runs a series of PSA Cryptography API test functions.
|
D | util_app_log.c | 10 #include "psa/crypto.h" 21 /* Generic PSA errors (psa/error.h). */ in al_psa_status() 83 /* PSA crypto errors (psa/crypto_values.h). */ in al_psa_status()
|
/Zephyr-latest/drivers/entropy/ |
D | Kconfig.psa_crypto | 4 # PSA Crypto Random source configuration options 7 bool "PSA Crypto Random source Entropy driver" 12 Enable the PSA Crypto source Entropy driver.
|
/Zephyr-latest/doc/services/storage/secure_storage/ |
D | index.rst | 7 …`Platform Security Architecture (PSA) Secure Storage API <https://arm-software.github.io/psa-api/s… 14 The secure storage subsystem makes the PSA Secure Storage API available on all board targets with 23 may secure the data stored via the PSA Secure Storage API at rest. 30 The secure storage subsystem's implementation of the PSA Secure Storage API: 50 …`3.2. Internal Trusted Storage requirements <https://arm-software.github.io/psa-api/storage/1.0/ov… 54 …(`2.4. The Internal Trusted Storage API <https://arm-software.github.io/psa-api/storage/1.0/overvi… 57 …(`2.2. Technical Background <https://arm-software.github.io/psa-api/storage/1.0/overview/architect… 68 * The data stored via the PSA Secure Storage API is not protected from direct 70 …`3.2. Internal Trusted Storage requirements <https://arm-software.github.io/psa-api/storage/1.0/ov… 78 To configure the implementation of the PSA Secure Storage API provided by Zephyr, have a look at the [all …]
|
/Zephyr-latest/doc/services/crypto/ |
D | psa_crypto.rst | 3 PSA Crypto 9 The PSA (Platform Security Architecture) Crypto API offers a portable 15 It is created and maintained by Arm. Arm developed the PSA as a 19 In Zephyr, the PSA Crypto API is implemented using Mbed TLS, an 33 The PSA Crypto API supports a wide range of cryptographic algorithms, 39 The PSA Crypto API includes robust key management features that 46 The PSA Crypto API abstracts the underlying cryptographic library, 53 By adhering to cryptographic agility, PSA Crypto ensures that 101 Most functions in the PSA Crypto API can return errors. All functions 142 In general, the PSA Crypto API allows either one writer or any number of [all …]
|
/Zephyr-latest/tests/subsys/secure_storage/psa/crypto/ |
D | testcase.yaml | 3 - psa.secure_storage 5 secure_storage.psa.crypto.secure_storage: 11 secure_storage.psa.crypto.tfm:
|
/Zephyr-latest/subsys/secure_storage/src/its/ |
D | CMakeLists.txt | 14 The PSA ITS encryption key provider in use generates keys by hashing the device ID 17 This means that the data and keys stored via the PSA APIs may not be secure at rest.") 20 The PSA ITS encryption key provider in use is not secure. 22 This means that the data and keys stored via the PSA APIs will not be secure at rest.
|
/Zephyr-latest/samples/tfm_integration/tfm_ipc/ |
D | sample.yaml | 27 - "The version of the PSA Framework API is" 28 - "The PSA Crypto service minor version is" 42 - "The version of the PSA Framework API is" 43 - "The PSA Crypto service minor version is"
|
/Zephyr-latest/modules/mbedtls/ |
D | create_psa_files.py | 14 "include", "psa", "crypto_config.h") 17 KCONFIG_PATH=os.path.join(SCRIPT_PATH, "Kconfig.psa.auto") 18 HEADER_PATH=os.path.join(SCRIPT_PATH, "configs", "config-psa.h") 31 Promptless symbol to state that there is a PSA crypto API provider 37 bool "All PSA crypto features" 63 # (see "modules/crypto/mbedtls/include/psa/crypto_adjust_config_key_pair_types.h"). 66 # - add _BASIC Kconfigs to Kconfig.psa.logic and let them "default y" as soon as 135 print("Error: PSA Kconfig and header files do not match with the current"
|
/Zephyr-latest/samples/tfm_integration/tfm_ipc/src/ |
D | main.c | 13 #include "psa/crypto.h" 17 * \brief Retrieve the version of the PSA Framework API. 29 printk("The version of the PSA Framework API is %d.\n", in tfm_get_version() 32 printk("The version of the PSA Framework API is not valid!\n"); in tfm_get_version() 53 printk("The PSA Crypto service minor version is %d.\n", version); in tfm_get_sid()
|
/Zephyr-latest/tests/bsim/bluetooth/mesh/ |
D | overlay_psa.conf | 1 # Increase the number of key slots in PSA Crypto core 4 # Enable mbedTLS PSA as a crypto backend
|
/Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
D | sample.yaml | 3 name: PSA Protected Storage 5 tags: psa 20 - "PSA Protected Storage API Version [0-9]*.[0-9]*"
|
1234567