Home
last modified time | relevance | path

Searched refs:policy (Results 1 – 23 of 23) sorted by relevance

/trusted-firmware-m-3.6.0/platform/ext/target/nxp/lpcxpresso55s69/Native_Driver/utilities/
Dfsl_notifier.c97 …FIER_SwitchConfig(notifier_handle_t *notifierHandle, uint8_t configIndex, notifier_policy_t policy) in NOTIFIER_SwitchConfig() argument
116 notifyBlock.policy = policy; in NOTIFIER_SwitchConfig()
135 if (policy != kNOTIFIER_PolicyForcible) in NOTIFIER_SwitchConfig()
147 if ((policy == kNOTIFIER_PolicyForcible) || (returnCode == kStatus_Success)) in NOTIFIER_SwitchConfig()
170 if (policy != kNOTIFIER_PolicyForcible) in NOTIFIER_SwitchConfig()
Dfsl_notifier.h100 notifier_policy_t policy; /*!< Configure transition policy. */ member
216 …IER_SwitchConfig(notifier_handle_t *notifierHandle, uint8_t configIndex, notifier_policy_t policy);
/trusted-firmware-m-3.6.0/secure_fw/partitions/crypto/
Dcrypto_library.c119 core->MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(usage) = in tfm_crypto_core_library_key_attributes_from_client()
121 core->MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(alg) = in tfm_crypto_core_library_key_attributes_from_client()
146 client_key_attr->usage = core.MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(usage); in tfm_crypto_core_library_key_attributes_to_client()
147 client_key_attr->alg = core.MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(alg); in tfm_crypto_core_library_key_attributes_to_client()
/trusted-firmware-m-3.6.0/docs/platform/cypress/psoc64/security/keys/
Dreadme.rst13 Use cysecuretools to generate new key pairs defined by the policy file,
20 cysecuretools -t cy8ckit-064s0s2-4343w -p policy/policy_multi_CM0_CM4_tfm.json create-keys
27 … cysecuretools -t cy8ckit-064s0s2-4343w -p policy/policy_multi_CM0_CM4_tfm.json re-provision-device
/trusted-firmware-m-3.6.0/lib/ext/t_cose/test/
Dt_cose_make_psa_test_key.c145 psa_key_policy_t policy = psa_key_policy_init(); in make_ecdsa_key_pair() local
146 psa_key_policy_set_usage(&policy, in make_ecdsa_key_pair()
149 crypto_result = psa_set_key_policy(key_handle, &policy); in make_ecdsa_key_pair()
/trusted-firmware-m-3.6.0/docs/platform/cypress/psoc64/
Dcypress_psoc64_spec.rst10 containing policy and secure keys. Please refer to the guide at
12 Use the following policy file for provisioning and signing:
199 If the board was previously provisioned with signing keys and policy, copy
217 provisioned policy allows board's re-provisioning.
230 cysecuretools -t cy8ckit-064s0s2-4343w -p policy/policy_multi_CM0_CM4_tfm.json create-keys
236 … cysecuretools -t cy8ckit-064s0s2-4343w -p policy/policy_multi_CM0_CM4_tfm.json re-provision-device
250 --policy platform/ext/target/cypress/psoc64/security/policy/policy_multi_CM0_CM4_tfm.json \
262 --policy platform/ext/target/cypress/psoc64/security/policy/policy_multi_CM0_CM4_tfm.json \
280 policy file for the actual ID's.
393 2. Create and copy rootCA files to "certificates" directory next to the policy
[all …]
/trusted-firmware-m-3.6.0/
DCMakeLists.txt13 # Armclang. Link: https://cmake.org/cmake/help/latest/policy/CMP0123.html
15 # Explictly set this policy to NEW behavior to eliminate long warnings. It shall be set in root
Dtoolchain_ARMCLANG.cmake136 # https://cmake.org/cmake/help/latest/policy/CMP0123.html
/trusted-firmware-m-3.6.0/docs/design_docs/
Dtfm_builtin_keys.rst52 policy dictated by the platform). Correctly abstracts away details of the key
66 policy restrictions for specific users of the keys, e.g. an NS entity, or a
174 that user on that particular key in the policy table. If no policies are
254 policy enforcement via ``tfm_plat_builtin_key_get_desc_table_ptr`` is currently
256 this policy or their own policy (Though this may be changed in future).
Dtfm_physical_attack_mitigation.rst521 to system policy. The introduction of one more checking point requires one
/trusted-firmware-m-3.6.0/docs/design_docs/dual-cpu/
Dtfm_multi_core_access_check.rst59 The check policy in Isolation Level 3 will be defined according to TF-M future
77 policy described in `Memory Access Check Policy`_ above.
309 access check policy.
324 - Or set ``is_valid = true`` and set ``is_secure`` according to platform specific policy.
352 access check policy.
398 access check policy.
Dmailbox_ns_agent_update.rst87 Services rely on the ``client_id`` to apply policy-checking, hence SPM
/trusted-firmware-m-3.6.0/platform/ext/target/cypress/psoc64/
Dinstall.cmake13 install(FILES ${TARGET_PLATFORM_PATH}/security/policy/policy_multi_CM0_CM4_tfm_dev_certs.json
/trusted-firmware-m-3.6.0/docs/security/
Dindex.rst45 TF-M policy is to credit the contributor's name in the published security advisory.
/trusted-firmware-m-3.6.0/platform/ext/target/cypress/psoc64/security/
Dreprov_helper.py169 def re_provision_device(device, policy): argument
/trusted-firmware-m-3.6.0/docs/integration_guide/services/
Dtfm_ps_integration_guide.rst15 The PS service implements an AES-GCM based AEAD encryption policy, as a
292 The encryption policy relies on a secret hardware unique key (HUK) per device.
319 The reference encryption policy is built on AES-GCM, and it **may** be replaced
Dtfm_secure_partition_addition.rst765 - In the IPC model, SPM will check the security policy and partition
/trusted-firmware-m-3.6.0/platform/
DCMakeLists.txt177 #TODO import policy
/trusted-firmware-m-3.6.0/cmake/
Dremote_library.cmake228 # See https://cmake.org/cmake/help/latest/policy/CMP0097.html for more info.
/trusted-firmware-m-3.6.0/platform/ns/
Dtoolchain_ns_ARMCLANG.cmake137 # https://cmake.org/cmake/help/latest/policy/CMP0123.html
/trusted-firmware-m-3.6.0/docs/design_docs/booting/
Dsecure_boot_rollback_protection.rst77 of the software issuer to define which policy to apply.
/trusted-firmware-m-3.6.0/platform/ext/target/cypress/psoc64/libs/core-lib/
DEULA53 …Cypress consistent with its Data Privacy Policy (www.cypress.com/privacy-policy), as updated or re…
/trusted-firmware-m-3.6.0/docs/security/threat_models/
Dgeneric_threat_model.rst647 | | It relies on NS OS to enhance scheduling policy and |