Home
last modified time | relevance | path

Searched refs:step (Results 1 – 25 of 35) sorted by relevance

12

/mbedtls/tests/suites/
A Dtest_suite_md.data291 generic multi step HMAC-MD5 Test Vector RFC2202 #1
295 generic multi step HMAC-MD5 Test Vector RFC2202 #2
299 generic multi step HMAC-MD5 Test Vector RFC2202 #3
303 generic multi step HMAC-MD5 Test Vector RFC2202 #4
307 generic multi step HMAC-MD5 Test Vector RFC2202 #5
311 generic multi step HMAC-MD5 Test Vector RFC2202 #6
315 generic multi step HMAC-MD5 Test Vector RFC2202 #7
1023 generic multi step SHA-1 Test Vector NIST CAVS #1
1027 generic multi step SHA-1 Test Vector NIST CAVS #2
1031 generic multi step SHA-1 Test Vector NIST CAVS #3
[all …]
A Dtest_suite_mps.data1 MPS Reader: Single step, single round, pausing disabled
4 MPS Reader: Single step, single round, pausing enabled but unused
7 MPS Reader: Single step, multiple rounds, pausing disabled
10 MPS Reader: Single step, multiple rounds, pausing enabled but unused
A Dtest_suite_psa_crypto_init.function36 size_t step;
45 if (state->step >= state->max_steps) {
49 *olen = MIN(len, state->length_sequence[state->step]);
53 ++state->step;
344 fake_entropy_state.step = 0;
A Dtest_suite_psa_crypto_pake.data77 PSA PAKE: unkown input step
81 PSA PAKE: invalid first input step
97 PSA PAKE: unkown output step
101 PSA PAKE: invalid first output step
A Dtest_suite_asn1parse.function576 unsigned int step = 0;
592 mbedtls_test_set_step(step);
604 ++step;
/mbedtls/library/
A Dpsa_crypto_pake.c284 psa_crypto_driver_pake_step_t step, in mbedtls_psa_pake_output_internal() argument
291 (void) step; // Unused parameter in mbedtls_psa_pake_output_internal()
310 if (step == PSA_JPAKE_X1_STEP_KEY_SHARE) { in mbedtls_psa_pake_output_internal()
347 if (step == PSA_JPAKE_X2S_STEP_KEY_SHARE && in mbedtls_psa_pake_output_internal()
373 if ((step == PSA_JPAKE_X2_STEP_ZK_PROOF) || in mbedtls_psa_pake_output_internal()
383 (void) step; in mbedtls_psa_pake_output_internal()
405 psa_crypto_driver_pake_step_t step, in mbedtls_psa_pake_input_internal() argument
410 (void) step; // Unused parameter in mbedtls_psa_pake_input_internal()
476 if (step == PSA_JPAKE_X2_STEP_ZK_PROOF) { in mbedtls_psa_pake_input_internal()
503 (void) step; in mbedtls_psa_pake_input_internal()
[all …]
A Dpsa_crypto_pake.h75 psa_crypto_driver_pake_step_t step,
113 psa_crypto_driver_pake_step_t step,
A Dpsa_crypto.c6732 switch (step) { in psa_hkdf_input()
6931 switch (step) { in psa_tls12_prf_input()
7042 switch (step) { in psa_tls12_prf_psk_to_ms_input()
7236 switch (step) { in psa_pbkdf2_input()
7260 switch (step) { in psa_key_derivation_check_input_type()
7378 (void) step; in psa_key_derivation_input_integer_internal()
8684 psa_pake_step_t step, in psa_jpake_prologue() argument
8702 if (step != computation_stage->step) { in psa_jpake_prologue()
8751 stage->step++; in psa_jpake_epilogue()
8799 (void) step; in psa_pake_output()
[all …]
A Dpsa_crypto_driver_wrappers.h2784 psa_crypto_driver_pake_step_t step, in psa_driver_wrapper_pake_output() argument
2793 return( mbedtls_psa_pake_output( &operation->data.ctx.mbedtls_ctx, step, in psa_driver_wrapper_pake_output()
2802 step, output, output_size, output_length ) ); in psa_driver_wrapper_pake_output()
2806 (void) step; in psa_driver_wrapper_pake_output()
2816 psa_crypto_driver_pake_step_t step, in psa_driver_wrapper_pake_input() argument
2825 step, input, in psa_driver_wrapper_pake_input()
2834 step, in psa_driver_wrapper_pake_input()
2839 (void) step; in psa_driver_wrapper_pake_input()
A Dssl_tls.c9255 for (psa_pake_step_t step = PSA_PAKE_STEP_KEY_SHARE; in mbedtls_psa_ecjpake_read_round() local
9256 step <= PSA_PAKE_STEP_ZK_PROOF; in mbedtls_psa_ecjpake_read_round()
9257 ++step) { in mbedtls_psa_ecjpake_read_round()
9266 status = psa_pake_input(pake_ctx, step, in mbedtls_psa_ecjpake_read_round()
9299 for (psa_pake_step_t step = PSA_PAKE_STEP_KEY_SHARE; in mbedtls_psa_ecjpake_write_round() local
9300 step <= PSA_PAKE_STEP_ZK_PROOF; in mbedtls_psa_ecjpake_write_round()
9301 ++step) { in mbedtls_psa_ecjpake_write_round()
9306 status = psa_pake_output(pake_ctx, step, in mbedtls_psa_ecjpake_write_round()
/mbedtls/tests/src/drivers/
A Dtest_driver_pake.c56 psa_crypto_driver_pake_step_t step, in mbedtls_test_transparent_pake_output() argument
85 operation, (libtestdriver1_psa_crypto_driver_pake_step_t) step, in mbedtls_test_transparent_pake_output()
90 operation, step, output, output_size, output_length); in mbedtls_test_transparent_pake_output()
93 (void) step; in mbedtls_test_transparent_pake_output()
106 psa_crypto_driver_pake_step_t step, in mbedtls_test_transparent_pake_input() argument
121 operation, (libtestdriver1_psa_crypto_driver_pake_step_t) step, in mbedtls_test_transparent_pake_input()
126 operation, step, input, input_length); in mbedtls_test_transparent_pake_input()
129 (void) step; in mbedtls_test_transparent_pake_input()
/mbedtls/tests/src/
A Dhelpers.c135 ++mbedtls_test_info.step; in mbedtls_test_increment_step()
144 unsigned long step; in mbedtls_test_get_step() local
150 step = mbedtls_test_info.step; in mbedtls_test_get_step()
156 return step; in mbedtls_test_get_step()
164 mbedtls_test_info.step = (unsigned long) (-1); in mbedtls_test_reset_step_internal()
167 void mbedtls_test_set_step(unsigned long step) in mbedtls_test_set_step() argument
173 mbedtls_test_info.step = step; in mbedtls_test_set_step()
/mbedtls/tests/include/test/drivers/
A Dpake.h56 psa_crypto_driver_pake_step_t step,
63 psa_crypto_driver_pake_step_t step,
/mbedtls/docs/architecture/
A Dpsa-storage-resilience.md65 … the same between the end of step 1 and the end of step 3, since the core must behave differently …
83 * Between step 3 and step 6: upon restart, the core needs to find out whether the secure element co…
84 * After step 6: the key has been created successfully.
96 * Between step 1 and step 4: upon restart, the core needs to find out whether the secure element co…
97 * After step 4: the key has been destroyed successfully.
276 * Start transaction, restart, recovery step 1, restart, recovery step 1, recovery step 2.
277 * Start transaction, restart, recovery step 1, restart, recovery step 1, restart, recovery step 1, …
278 …saction, restart, recovery step 1, restart, recovery step 1, restart, recovery step 1, restart, re…
283 …step. For example, if we have confidence that recovery step 1 is idempotent (i.e. doing it twice i…
365 In addition, before or after step 2, create or remove the key file in the internal storage.
[all …]
A Dpsa-crypto-implementation-structure.md66 In case of any error occurring at step 3 or 4, psa_fail_key_creation() is called. It wipes and clea…
103 … part of the official PSA Cryptography specification. Therefore the first step before implementing…
/mbedtls/tests/include/test/
A Dhelpers.h76 unsigned long step; member
241 void mbedtls_test_set_step(unsigned long step);
/mbedtls/include/psa/
A Dcrypto.h3383 psa_key_derivation_step_t step,
3426 psa_key_derivation_step_t step,
3494 psa_key_derivation_step_t step,
3562 psa_key_derivation_step_t step,
A Dcrypto_extra.h1462 psa_pake_step_t step,
1517 psa_pake_step_t step,
1827 psa_pake_step_t MBEDTLS_PRIVATE(step);
/mbedtls/docs/architecture/psa-migration/
A Dstrategy.md263 Note: the fact that step 1 is not achieved for all of libmbedcrypto (see
271 not possible to achieve good test coverage at the end of step 1 or step 2, it
272 is preferable to group with the next step(s) in the same PR until good test
285 - Step 2 is achieved for most of X.509 and TLS (same gaps as step 1) when
289 **Strategy for step 1:**
302 **Strategy for step 2:**
316 **Strategy for step 3:**
340 Executing step 3 will mostly consist of using the right dependency macros in
353 There is however a risk, especially in step 3 where we change how dependencies
359 the same before and after the PR that implements step 3. This is tested
[all …]
/mbedtls/docs/proposed/
A Dpsa-driver-interface.md366 psa_key_derivation_step_t step);
380 psa_key_derivation_step_t step,
384 psa_key_derivation_step_t step,
388 psa_key_derivation_step_t step,
393 psa_key_derivation_step_t step,
400 * The `step` parameter indicates the input step whose content the driver wants to retrieve.
435 psa_key_derivation_step_t step,
698 * `step` computation step based on which driver should perform an action.
704 `step` can be one of the following values:
718                             psa_crypto_driver_pake_step_t step,
[all …]
/mbedtls/scripts/data_files/driver_templates/
A Dpsa_crypto_driver_wrappers.h.jinja2747 psa_crypto_driver_pake_step_t step,
2756 return( mbedtls_psa_pake_output( &operation->data.ctx.mbedtls_ctx, step,
2765 step, output, output_size, output_length ) );
2769 (void) step;
2779 psa_crypto_driver_pake_step_t step,
2788 step, input,
2797 step,
2802 (void) step;
/mbedtls/docs/architecture/psa-thread-safety/
A Dpsa-thread-safety.md61 …tion, where the same key identifier was used as a parameter to a previous step in the multi-part o…
207 …_key_slot`, if a slot has been found then the slot id is set. This second step is not done under t…
222 … copying the key into a separate buffer to be used by the operation. This step is not performed un…
237 …nt" for each call, this is a single execution step where the function takes effect (this is usuall…
257 Although the `step` feature used in some tests is thread-safe, it may produce unexpected results fo…
/mbedtls/docs/
A Dpsa-transition.md352 2. Call one of the key creation functions, passing the attributes defined in the previous step, to …
540 2. Call one of the key creation functions, passing the attributes defined in the previous step, to …
602 …c15a) instead for an input that is a PSA key object.) The input step value for each step is as fol…
603 … for the salt used during the extraction step. Omit this step for HKDF-Expand. For HKDF, you may o…
605 …69233f4b779acb5b7d) for the info string used during the expansion step. Omit this step for HKDF-Ex…
615 3. Call `psa_key_derivation_input_cost` with the step `PSA_KEY_DERIVATION_INPUT_COST` to select the…
616 …c15a) instead for an input that is a PSA key object.) The input step value for each step is as fol…
617 …3562c3947a752470d4a) for the salt used during the extraction step. You may repeat this step to pas…
672 2. Call one of the key creation functions, passing the attributes defined in the previous step, to …
802 You can use the PK module as an intermediate step to create an RSA or ECC key for use with PSA. Thi…
[all …]
A Dpsa-driver-example-and-guide.md16 …step (one function call), such as verifying a signature, are called *Single-Part Operations*. On t…
/mbedtls/3rdparty/p256-m/p256-m/
A DREADME.md386 addition/subtraction is performed at each step. Again, care is taken to make
483 a standard optimisation to save one multiplication in the first step of

Completed in 76 milliseconds

12