| /mbedtls-latest/library/ |
| D | psa_crypto_se.c | 49 psa_drv_se_context_t context; member
84 return &driver->u.context; in psa_get_se_driver_context()
96 *p_drv_context = (driver ? &driver->u.context : NULL); in psa_get_se_driver()
210 status = p_validate_slot_number(&driver->u.context, in psa_find_se_slot_for_key()
226 status = p_allocate(&driver->u.context, in psa_find_se_slot_for_key()
252 &driver->u.context, in psa_destroy_se_key()
270 &driver->u.context, in psa_init_all_se_drivers()
|
| /mbedtls-latest/tests/suites/ |
| D | test_suite_psa_crypto_se_driver_hal.function | 144 psa_drv_se_context_t *context,
150 (void) context;
166 static psa_status_t counter_allocate(psa_drv_se_context_t *context,
175 if (context->persistent_data_size != sizeof(psa_key_slot_number_t)) {
189 static psa_status_t null_import(psa_drv_se_context_t *context,
196 (void) context;
209 static psa_status_t null_generate(psa_drv_se_context_t *context,
216 (void) context;
231 static psa_status_t null_destroy(psa_drv_se_context_t *context,
235 (void) context;
[all …]
|
| D | test_suite_psa_crypto_se_driver_hal_mocks.function | 165 static psa_status_t mock_export(psa_drv_se_context_t *context,
171 (void) context;
182 static psa_status_t mock_export_public(psa_drv_se_context_t *context,
188 (void) context;
199 static psa_status_t mock_sign(psa_drv_se_context_t *context,
208 (void) context;
222 static psa_status_t mock_verify(psa_drv_se_context_t *context,
230 (void) context;
261 static psa_status_t mock_destroy(psa_drv_se_context_t *context,
265 (void) context;
|
| D | test_suite_pk.function | 244 /** Setup the provided PK context.
251 * \param pk_type mbedtls_pk_type_t to use in the PK context.
735 /* test that freeing the context does not destroy the key */
863 /* In informational functions, we accept NULL where a context pointer
1037 /* Turn the prv PK context into an opaque one.*/
1440 /* init pk-rsa context */
1458 /* init pk-rsa context */
1517 /* init pk-rsa context */
1582 /* init pk-rsa context */
1603 /* Turn PK context into an opaque one. */
[all …]
|
| D | test_suite_aes.function | 4 /* Test AES with a copied context.
6 * master, enc and dec must be AES context objects. They don't need to
22 // Set key and encrypt with original context
30 // Set key for decryption with original context
36 // Wipe the original context to make sure nothing from it is used
39 // Encrypt with copied context
45 // Decrypt with copied context
649 /* We test context copying multiple times, with different alignments
|
| D | test_suite_entropy.function | 8 DUMMY_CONSTANT_LENGTH, /* Output context->length bytes */
28 entropy_dummy_context *context = arg;
29 ++context->calls;
31 switch (context->instruction) {
33 *olen = context->length;
|
| D | test_suite_cipher.function | 96 * it, and instead start with a fresh context.
531 /* Initialise context */
588 /* Initialise context */
806 /* Prepare context */
918 * Prepare context for decryption
985 /* prepare context for encryption */
1065 /* Prepare context */
1104 /* Prepare context */
1166 /* build a fake context just for getting access to get_padding */
|
| D | test_suite_block_cipher.function | 53 /* Now properly setup the context */
86 * did not change the state of the context.) */
|
| D | test_suite_aes.ecb.data | 280 AES-128-ECB Copy context
283 AES-192-ECB Copy context
287 AES-256-ECB Copy context
|
| D | test_suite_pkwrite.function | 134 /* Turn the key PK context into an opaque one.
221 /* Turn the priv_key PK context into an opaque one. */
|
| D | test_suite_shax.data | 2384 SHA3-224 context reuse
2387 SHA3-256 context reuse
2390 SHA3-384 context reuse
2393 SHA3-512 context reuse
2396 # Test a subset of the 12 possible cross-size context reuse, with both
2398 SHA3-224 to SHA3-256 context reuse
2401 SHA3-256 to SHA3-512 context reuse
2404 SHA3-512 to SHA3-384 context reuse
2407 SHA3-384 to SHA3-224 context reuse
|
| D | test_suite_dhm.function | 23 * DHM context by the caller). */
54 * against the context. */
|
| D | test_suite_chacha20.function | 54 /* Don't free/init the context nor set the key again,
|
| D | test_suite_random.data | 23 # because CTR_DRBG crashes when given an unseeded context. This is arguably
|
| /mbedtls-latest/docs/architecture/ |
| D | alternative-implementations.md | 38 * Create a header file `xxx_alt.h` that defines the context type(s) used by the module. For example…
43 ### Constraints on context types
45 …context types to any C type except incomplete and array types (although they would normally be `st…
47 Where a context type needs to have a certain field, the field must have the same type and semantics…
54 …context object in memory (except during the execution of a library function that takes this contex…
64 In practice, this means that a pointer to a context or to a part of a context does not remain valid…
78 … you must use the same layout for context objects as the built-in implementation. If you want to u…
|
| D | tls13-support.md | 379 fields of the SSL context or based on the reading of the type of the next
383 reading to not modify the SSL context as this stage may be repeated if the
393 * pre-processing stage: prepare the SSL context for the message parsing. This
400 update of the SSL context. The idea of the pre-processing/parsing/post-processing
405 context to prepare for the next incoming and outgoing messages. This stage is
417 optional. The check is based on the value of some fields of the SSL context.
424 of the SSL context. The idea of the preparation/writing/finalization
429 context to prepare for the next incoming and outgoing messages. This stage is
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 189 2. `const uint8_t *key_buffer`: a key material or key context buffer.
196 …a_key_id_t *` output parameter is replaced by a sequence of parameters that convey the key context:
197 1. `uint8_t *key_buffer`: a buffer for the key material or key context.
240 …resents the operation context. The lifecycle of a driver operation context is similar to the lifec…
242 1. The core initializes operation context objects to either all-bits-zero or to logical zero (`{0}`…
243 …or this operation family. If this fails, the core destroys the operation context object without ca…
244 1. The core calls other entry points that manipulate the operation context object, respecting the c…
245 …bort` entry point for this operation family, then destroys the operation context object without ca…
246 1. If a “finish” entry point fails, the core destroys the operation context object without calling …
258 …h_operation_t"`: the type of a hash operation context. It must be possible to copy a hash operatio…
[all …]
|
| /mbedtls-latest/tests/scripts/ |
| D | components-configuration.sh | 52 tests/context-info.sh
74 tests/context-info.sh
101 tests/context-info.sh
129 tests/context-info.sh
|
| /mbedtls-latest/docs/ |
| D | tls13-early-data.md | 33 where ssl is the SSL context to use, data_to_write the address of the data
35 not be completed, not even started for the SSL context ssl when the function is
73 specifically by the user of write_early_data(). A fresh SSL context (typically
159 context to use:
|
| D | use-psa-crypto.md | 73 wrap a PSA key pair into a PK context. The key can be used for private-key
81 **Use in X.509 and TLS:** opt-in. The application needs to construct the PK context
83 resulting context to the following existing APIs:
119 There is a new API function `mbedtls_cipher_setup_psa()` to set up a context
|
| /mbedtls-latest/tests/src/ |
| D | fake_external_rng_for_test.c | 30 mbedtls_psa_external_random_context_t *context, in mbedtls_psa_external_get_random() argument
33 (void) context; in mbedtls_psa_external_get_random()
|
| /mbedtls-latest/tests/src/test_helpers/ |
| D | ssl_helpers.c | 487 mbedtls_test_message_socket_context *context = in mbedtls_test_mock_tcp_send_msg() local
490 if (context == NULL || context->socket == NULL in mbedtls_test_mock_tcp_send_msg()
491 || context->queue_output == NULL) { in mbedtls_test_mock_tcp_send_msg()
495 queue = context->queue_output; in mbedtls_test_mock_tcp_send_msg()
496 socket = context->socket; in mbedtls_test_mock_tcp_send_msg()
514 mbedtls_test_message_socket_context *context = in mbedtls_test_mock_tcp_recv_msg() local
520 if (context == NULL || context->socket == NULL in mbedtls_test_mock_tcp_recv_msg()
521 || context->queue_input == NULL) { in mbedtls_test_mock_tcp_recv_msg()
525 queue = context->queue_input; in mbedtls_test_mock_tcp_recv_msg()
526 socket = context->socket; in mbedtls_test_mock_tcp_recv_msg()
[all …]
|
| /mbedtls-latest/docs/architecture/psa-migration/ |
| D | psa-legacy-bridges.md | 160 …re detailed in “[API to create a PSA key from a PK context](#api-to-create-a-psa-key-from-a-pk-con…
162 #### Using a PSA key as a PK context
177 Gap: a way to copy a PSA key into a PK context. This can only be expected to work if the PSA key is…
247 #### API to create a PSA key from a PK context
251 …context has incomplete algorithm information. For example, there is no way to distinguish between …
256 …llment algorithm. The intended usage flags cannot be deduced from the PK context either, but the c…
276 * `mbedtls_pk_get_psa_attributes` sets the type and size based on what's in the pk context.
277 …ey pair if the context contains a private key and the indicated usage is a private-key usage. The …
295 #### API to copy a PSA key to a PK context
297 Based on the [gap analysis](#using-a-psa-key-as-a-pk-context):
[all …]
|
| D | md-cipher-dispatch.md | 222 * How to perform the operation (context type, which functions to call).
376 - We carry over questionable implementation decisions, like dynamic allocation of context.
446 #### Support for PSA in the MD context
448 An MD context needs to contain either a legacy module's context (or a pointer to one, as is the cas…
450 …r indirection, but this means that an MD context would always be as large as the largest supported…
472 …e availability of the accelerator when the context is set up. This choice needs to be recorded in …
503 Each function that performs some hash operation or context management needs to know whether to disp…
505 If given an established context, use its `engine` field.
601 A block cipher context contains either a legacy module's context (AES, ARIA, Camellia) or a PSA key…
603 …e availability of the accelerator when the context is set up. This choice needs to be recorded in …
[all …]
|
| D | strategy.md | 180 - Provide a new way to set up a context that causes operations on that context
183 be changed when setting up the context, but not when using it. In
185 key to be passed as a context of this layer (eg, `mbedtls_pk_context`).
187 - Downside: when the context is typically set up by the application, requires
190 This strategy is not useful when no context is used, for example with the
394 same context type for hashes and HMACs, while the PSA API (rightfully) has
395 distinct operation types. Similarly, the Cipher layer uses the same context
402 introducing new context types) would provide to users.
433 bytes in the X.509 CRT structure, and only moved to a PK context / PSA slot
468 would need a way to easily extract the PSA key ID from the PK context.
|
