Home
last modified time | relevance | path

Searched refs:context (Results 1 – 25 of 44) sorted by relevance

12

/mbedtls-3.6.0/library/
Dpsa_crypto_se.c49 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-3.6.0/docs/architecture/
Dalternative-implementations.md38 * 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…
Dtls13-support.md418 fields of the SSL context or based on the reading of the type of the next
422 reading to not modify the SSL context as this stage may be repeated if the
432 * pre-processing stage: prepare the SSL context for the message parsing. This
439 update of the SSL context. The idea of the pre-processing/parsing/post-processing
444 context to prepare for the next incoming and outgoing messages. This stage is
456 optional. The check is based on the value of some fields of the SSL context.
463 of the SSL context. The idea of the preparation/writing/finalization
468 context to prepare for the next incoming and outgoing messages. This stage is
509 where ssl is the SSL context to use, data_to_write the address of the data
511 not be completed, not even started for the SSL context ssl when the function is
[all …]
/mbedtls-3.6.0/tests/suites/
Dtest_suite_psa_crypto_se_driver_hal.function131 psa_drv_se_context_t *context,
137 (void) context;
153 static psa_status_t counter_allocate(psa_drv_se_context_t *context,
162 if (context->persistent_data_size != sizeof(psa_key_slot_number_t)) {
176 static psa_status_t null_import(psa_drv_se_context_t *context,
183 (void) context;
196 static psa_status_t null_generate(psa_drv_se_context_t *context,
203 (void) context;
218 static psa_status_t null_destroy(psa_drv_se_context_t *context,
222 (void) context;
[all …]
Dtest_suite_psa_crypto_se_driver_hal_mocks.function165 psa_status_t mock_export(psa_drv_se_context_t *context,
171 (void) context;
182 psa_status_t mock_export_public(psa_drv_se_context_t *context,
188 (void) context;
199 psa_status_t mock_sign(psa_drv_se_context_t *context,
208 (void) context;
222 psa_status_t mock_verify(psa_drv_se_context_t *context,
230 (void) context;
261 psa_status_t mock_destroy(psa_drv_se_context_t *context,
265 (void) context;
Dtest_suite_pk.function291 /* test that freeing the context does not destroy the key */
419 /* In informational functions, we accept NULL where a context pointer
951 /* init pk-rsa context */
968 /* init pk-rsa context */
1023 /* init pk-rsa context */
1078 /* init pk-rsa context */
1094 /* Turn PK context into an opaque one. */
1194 * An rsa_alt context can only do private operations (decrypt, sign).
1196 * corresponding rsa context.
1217 /* Initialize PK RSA context with random key */
[all …]
Dtest_suite_aes.function4 /* Test AES with a copied context.
6 * master, enc and dec must be AES context objects. They don't need to
21 // Set key and encrypt with original context
29 // Set key for decryption with original context
35 // Wipe the original context to make sure nothing from it is used
38 // Encrypt with copied context
44 // Decrypt with copied context
529 /* We test context copying multiple times, with different alignments
Dtest_suite_entropy.function8 DUMMY_CONSTANT_LENGTH, /* Output context->length bytes */
28 entropy_dummy_context *context = arg;
29 ++context->calls;
31 switch (context->instruction) {
33 *olen = context->length;
Dtest_suite_aes.ecb.data280 AES-128-ECB Copy context
283 AES-192-ECB Copy context
287 AES-256-ECB Copy context
Dtest_suite_cipher.function96 * it, and instead start with a fresh context.
527 /* Initialise context */
580 /* Initialise context */
798 /* Prepare context */
906 * Prepare context for decryption
973 /* prepare context for encryption */
1053 /* Prepare context */
1092 /* Prepare context */
1154 /* build a fake context just for getting access to get_padding */
Dtest_suite_chacha20.function54 /* Don't free/init the context nor set the key again,
Dtest_suite_poly1305.function46 /* Don't free/init the context, in order to test that starts() does the
Dtest_suite_random.data23 # because CTR_DRBG crashes when given an unseeded context. This is arguably
Dtest_suite_dhm.function23 * DHM context by the caller). */
54 * against the context. */
Dtest_suite_shax.data2384 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
Dtest_suite_rsa.function1000 /* Original MPI's with which we set up the RSA context */
1024 /* Setup RSA context */
1069 /* If we were providing enough information to setup a complete private context,
1124 /* Original MPI's with which we set up the RSA context */
1191 /* Setup RSA context */
1221 /* If we were providing enough information to setup a complete private context,
/mbedtls-3.6.0/tests/src/
Dfake_external_rng_for_test.c30 mbedtls_psa_external_random_context_t *context, in mbedtls_psa_external_get_random() argument
33 (void) context; in mbedtls_psa_external_get_random()
/mbedtls-3.6.0/docs/
Duse-psa-crypto.md73 wrap a PSA key pair into a PK context. The key can be used for private-key
82 with a context set this way, while they would be available with a normal
83 context: `mbedtls_pk_check_pair()`, `mbedtls_pk_debug()`, all public key
86 **Use in X.509 and TLS:** opt-in. The application needs to construct the PK context
88 resulting context to the following existing APIs:
124 There is a new API function `mbedtls_cipher_setup_psa()` to set up a context
/mbedtls-3.6.0/tests/src/test_helpers/
Dssl_helpers.c497 mbedtls_test_message_socket_context *context = in mbedtls_test_mock_tcp_send_msg() local
500 if (context == NULL || context->socket == NULL in mbedtls_test_mock_tcp_send_msg()
501 || context->queue_output == NULL) { in mbedtls_test_mock_tcp_send_msg()
505 queue = context->queue_output; in mbedtls_test_mock_tcp_send_msg()
506 socket = context->socket; in mbedtls_test_mock_tcp_send_msg()
524 mbedtls_test_message_socket_context *context = in mbedtls_test_mock_tcp_recv_msg() local
530 if (context == NULL || context->socket == NULL in mbedtls_test_mock_tcp_recv_msg()
531 || context->queue_input == NULL) { in mbedtls_test_mock_tcp_recv_msg()
535 queue = context->queue_input; in mbedtls_test_mock_tcp_recv_msg()
536 socket = context->socket; in mbedtls_test_mock_tcp_recv_msg()
[all …]
/mbedtls-3.6.0/docs/proposed/
Dpsa-driver-interface.md189 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-3.6.0/tests/data_files/base64/
Dsrv_def.txt1 // Server context with default MbedTLS configuration
Dcli_def.txt1 // Client context with default MbedTLS configuration
/mbedtls-3.6.0/docs/architecture/psa-migration/
Dstrategy.md180 - 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.
Dmd-cipher-dispatch.md166 * How to perform the operation (context type, which functions to call).
330 #### Support for PSA in the MD context
332 An MD context needs to contain either a legacy module's context (or a pointer to one, as is the cas…
334 …r indirection, but this means that an MD context would always be as large as the largest supported…
356 …e availability of the accelerator when the context is set up. This choice needs to be recorded in …
387 Each function that performs some hash operation or context management needs to know whether to disp…
389 If given an established context, use its `engine` field.
/mbedtls-3.6.0/tests/include/test/
Dssl_helpers.h451 mbedtls_test_message_socket_context *context);

12