| /trusted-firmware-m-3.4.0/secure_fw/partitions/crypto/ |
| D | crypto_alloc.c | 34 static struct tfm_crypto_operation_s operations[CRYPTO_CONC_OPER_NUM] = {{0}}; variable
47 (void)memset((uint8_t *)&(operations[index].operation), 0, in memset_operation_context()
48 sizeof(operations[index].operation)); in memset_operation_context()
61 (void)memset(operations, 0, sizeof(operations)); in tfm_crypto_init_alloc()
90 if (operations[i].in_use == TFM_CRYPTO_NOT_IN_USE) { in tfm_crypto_operation_alloc()
91 operations[i].in_use = TFM_CRYPTO_IN_USE; in tfm_crypto_operation_alloc()
92 operations[i].owner = partition_id; in tfm_crypto_operation_alloc()
93 operations[i].type = type; in tfm_crypto_operation_alloc()
95 *ctx = (void *) &(operations[i].operation); in tfm_crypto_operation_alloc()
122 if ((operations[h_val - 1].in_use == TFM_CRYPTO_IN_USE) && in tfm_crypto_operation_release()
[all …]
|
| D | Kconfig | 19 int "Max number of concurrent operations"
22 The max number of concurrent operations that can be active (allocated)
73 bool "Only enable multi-part operations"
76 Only enable multi-part operations in Hash, MAC, AEAD and symmetric
|
| /trusted-firmware-m-3.4.0/docs/security/security_advisories/ |
| D | crypto_multi_part_ops_abort_fail.rst | 6 | | multi-part MAC/hashing/cipher operations. |
36 operations. The sequence can be simplified to the following steps:
55 multi-part crypto operations. For example, ``psa_mac_operation_t`` for
56 multi-part MAC operations and ``psa_hash_operation_t`` for multi-part hashing
57 operations.
62 stores and manages the context of ongoing multi-part crypto operations in the
99 During multi-part hashing/MAC/cipher operations, if the underlying crypto
133 operations in the underlying crypto library.
140 - Multi-part hashing operations
147 - Multi-part MAC operations
[all …]
|
| /trusted-firmware-m-3.4.0/docs/integration_guide/services/ |
| D | tfm_crypto_integration_guide.rst | 32 operations
33 - ``crypto_hash.c`` : This module handles requests for hashing operations
34 - ``crypto_mac.c`` : This module handles requests for MAC operations
35 - ``crypto_aead.c`` : This module handles requests for AEAD operations
37 related operations
39 related operations
40 - ``crypto_key.c`` : This module handles requests for key backend operations,
43 cryptographic operations
56 for multipart operations (8 for the current implementation). For multipart
57 cipher/hash/MAC/generator operations, a context is associated to the handle
[all …]
|
| D | tfm_ps_integration_guide.rst | 169 - ``crypto/ps_crypto_interface.h`` - Abstracts the cryptographic operations for
173 operations with calls to the TF-M Crypto service.
182 counters operations. This API detaches the use of NV counters from the TF-M NV
249 limitation to provide power failure safe update operations.
318 The PS service cryptographic operations are implemented in
|
| /trusted-firmware-m-3.4.0/docs/platform/cypress/psoc64/libs/core-lib/ |
| D | README.md | 29 … for setting a register with a name field and value for providing get-clear-modify-write operations
30 …_SET`: Uses _CLR_SET_FLD32U macro for providing get-clear-modify-write operations with a name fiel…
31 …tting a 16-bit register with a name field and value for providing get-clear-modify-write operations
32 …_SET`: Uses _CLR_SET_FLD16U macro for providing get-clear-modify-write operations with a name fiel…
33 …etting a 8-bit register with a name field and value for providing get-clear-modify-write operations
34 …* `CY_REG8_CLR_SET`: Uses _CLR_SET_FLD8U macro for providing get-clear-modify-write operations wit…
|
| D | RELEASE.md | 25 … for setting a register with a name field and value for providing get-clear-modify-write operations
26 …* CY_REG32_CLR_SET: Uses _CLR_SET_FLD32U macro for providing get-clear-modify-write operations wit…
27 …tting a 16-bit register with a name field and value for providing get-clear-modify-write operations
28 …* CY_REG16_CLR_SET: Uses _CLR_SET_FLD16U macro for providing get-clear-modify-write operations wit…
29 …etting a 8-bit register with a name field and value for providing get-clear-modify-write operations
30 …* CY_REG8_CLR_SET: Uses _CLR_SET_FLD8U macro for providing get-clear-modify-write operations with …
|
| /trusted-firmware-m-3.4.0/docs/technical_references/design_docs/dual-cpu/ |
| D | communication_prototype_between_nspe_and_spe_in_dual_core_systems.rst | 130 should protect concurrent operations from the other core.
184 operations, such as interrupt EOI or acknowledge.
222 hook its specific mailbox operations. When TF-M SPM invokes RPC APIs to deal
224 mailbox operations.
247 eventually execute specific mailbox message handling operations. The mailbox
254 guarantee that the operations are not interfered by NSPE mailbox operations
316 mailbox reply operations. The mailbox reply functions must not trigger context
476 Mailbox operations callbacks
479 This structures contains the callback functions for specific mailbox operations.
492 This function registers underlying mailbox operations into TF-M RPC callbacks.
[all …]
|
| /trusted-firmware-m-3.4.0/docs/technical_references/design_docs/ |
| D | tfm_its_512_flash.rst | 13 devices, imposing a requirement for word-aligned full-block program operations,
64 incomplete program operations, as well as write bytes in a sequential order.
|
| D | stateless_rot_service.rst | 118 3. This API performs some operations as ``psa_connect()`` does, such as the
146 service is a one-shot connection. These services provide standalone operations
158 TF-M native services are used widely. They only need standalone operations and
|
| D | secure_partition_manager.rst | 187 on sequence, then `SPM` takes over the execution to perform these operations:
203 operations, such as:
235 This procedure initializes necessary runtime operations such as memory
262 service routines can avoid special operations.
389 - The `FF-M` subroutine performs `FF-M` defined operations.
390 - The backend operations perform target partition runtime model decided
391 operations. For example, enqueue message into the target partition under
400 is an ideal place for subsequent operations such as context switching.
415 * Check if extra operations are required
467 common service costs much memory, and runtime operations(allocation and
[all …]
|
| D | hardware_abstraction_layer.rst | 14 operations on the :term:`SPE` side and provides a set of APIs to the upper
19 In some cases, although the operations are defined architecturally,
23 operations as well.
83 Part of the :term:`HAL` interfaces does not focus on exact hardware operations
299 set-up operations only.
302 operations.
304 The boundary operations are abstracted as HAL interfaces because isolation
592 The SPM HAL interrupt APIs are intended for operations on Interrupt Controllers
|
| D | tfm_crypto_design.rst | 56 …| | operations in the Secure world. | …
62 …| | multipart operations, and dispatching to the corresponding | ``…
165 …| | | for multi-part operations, that…
|
| D | ps_key_management.rst | 32 Crypto service to perform AEAD encryption and/or decryption operations using the
77 - It is simple and efficient, requiring only two HMAC operations when the length
|
| D | symmetric_initial_attest.rst | 118 ``attest_symmetric_key.c`` to handle symmetric Instance ID related operations.
300 HMAC operations are added in ``crypto_adapters/t_cose_psa_crypto.c``.
304 - ``T_COSE_ENABLE_SIGN1`` selects ECDSA and Hash operations for
306 - ``T_COSE_ENABLE_MAC0`` selects HMAC operations for ``COSE_Mac0``.
|
| D | tfm_physical_attack_mitigation.rst | 235 against critical operations in :term:`SPE` workflow and critical modules in
238 Those critical operations and modules either directly access the assets or
239 protect the assets from disclosure. Those operations and modules can include:
243 - Cryptographic operations
244 - TF-M Secure Storage operations
334 Since crypto operations are done by mbedTLS library or by a custom crypto
336 physical attacks against crypto operations is out-of-scope for this document.
|
| /trusted-firmware-m-3.4.0/docs/integration_guide/ |
| D | os_migration_guide_armv8m.rst | 16 operations.
|
| /trusted-firmware-m-3.4.0/docs/configuration/profiles/ |
| D | tfm_profile_small.rst | 44 Associated Data (AEAD) operations.
159 Cryptography API [13]_ in hash, symmetric ciphers, MAC and AEAD operations.
161 Multi-part operations allows the message data to be processed in fragments
164 length. Therefore single-part operations can help users optimize memory
170 enable single-part operations by toggling Profile Small default configuration.
173 functionality with single-part operations, compared to with multi-part ones.
174 Users can enable single-part operations if the usage scenario requires
382 - Disable single-part operations in Hash, MAC, AEAD and symmetric ciphers
500 …| ``TFM_CRYPTO_TEST_SINGLE_PART_FUNCS`` | ``OFF`` | Test single-part operations in hash…
|
| D | tfm_profile_medium.rst | 231 … | encryption operations |
301 …| ``TFM_CRYPTO_TEST_SINGLE_PART_FUNCS`` | ``OFF`` | Test single-part operations in hash…
321 - Hash operations
324 - AEAD operations
|
| /trusted-firmware-m-3.4.0/config/ |
| D | cp_config_default.cmake | 18 …# Set float abi soft, meaning software library functions for floating-point operations and softwar…
|
| /trusted-firmware-m-3.4.0/docs/ |
| D | glossary.rst | 14 Interface to abstract hardware-oriented operations and provides a set of
25 `PSA term`_. A set of related security operations that are implemented
|
| /trusted-firmware-m-3.4.0/docs/releases/ |
| D | release_process.rst | 18 verify their platforms and confirm the correct operations or provide fixes
|
| D | 1.4.0.rst | 24 'abort' function may not take effect in some TF-M Crypto multi-part operations
|
| /trusted-firmware-m-3.4.0/docs/security/ |
| D | security.rst | 53 | | multi-part MAC/hashing/cipher operations. |
|
| /trusted-firmware-m-3.4.0/lib/ext/tf-m-tests/ |
| D | Kconfig | 243 bool "Test single-part operations in hash, MAC, AEAD and symmetric ciphers"
|
