Home
last modified time | relevance | path

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

12

/mbedtls-latest/tests/suites/
Dtest_suite_md.data203 generic multi step mbedtls_md5 Test vector RFC1321 #1
207 generic multi step mbedtls_md5 Test vector RFC1321 #2
211 generic multi step mbedtls_md5 Test vector RFC1321 #3
215 generic multi step mbedtls_md5 Test vector RFC1321 #4
219 generic multi step mbedtls_md5 Test vector RFC1321 #5
223 generic multi step mbedtls_md5 Test vector RFC1321 #6
227 generic multi step mbedtls_md5 Test vector RFC1321 #7
231 generic multi step mbedtls_ripemd160 Test vector from paper #1
235 generic multi step mbedtls_ripemd160 Test vector from paper #2
239 generic multi step mbedtls_ripemd160 Test vector from paper #3
[all …]
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
Dtest_suite_psa_crypto_init.function53 size_t step;
62 if (state->step >= state->max_steps) {
66 *olen = MIN(len, state->length_sequence[state->step]);
70 ++state->step;
372 fake_entropy_state.step = 0;
Dtest_suite_psa_crypto_pake.data77 PSA PAKE: unknown input step
81 PSA PAKE: invalid first input step
97 PSA PAKE: unknown output step
101 PSA PAKE: invalid first output step
Dtest_suite_asn1parse.function576 unsigned int step = 0;
592 mbedtls_test_set_step(step);
604 ++step;
Dtest_suite_psa_crypto.data5348 PSA key derivation: HKDF-SHA-256, duplicate salt step
5352 PSA key derivation: HKDF-SHA-256, duplicate secret step (direct, direct)
5356 PSA key derivation: HKDF-SHA-256, duplicate secret step (direct, key)
5360 PSA key derivation: HKDF-SHA-256, duplicate secret step (key, direct)
5364 PSA key derivation: HKDF-SHA-256, duplicate secret step (key, key)
5368 PSA key derivation: HKDF-SHA-256, duplicate info step (non-consecutive)
5372 PSA key derivation: HKDF-SHA-256, duplicate info step (consecutive)
5376 PSA key derivation: HKDF-SHA-256, reject label step
5380 PSA key derivation: HKDF-SHA-256, reject seed step
5388 PSA key derivation: HKDF-SHA-256, reject input cost step using input_bytes
[all …]
/mbedtls-latest/library/
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()
322 } else if (step == PSA_JPAKE_X2S_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()
374 (step == PSA_JPAKE_X2S_STEP_ZK_PROOF)) { in mbedtls_psa_pake_output_internal()
383 (void) step; in mbedtls_psa_pake_output_internal()
392 psa_crypto_driver_pake_step_t step, in mbedtls_psa_pake_output() argument
398 operation, step, output, output_size, output_length); in mbedtls_psa_pake_output()
[all …]
Dpsa_crypto.c6801 psa_key_derivation_step_t step, argument
6807 switch (step) {
7002 psa_key_derivation_step_t step, argument
7006 switch (step) {
7113 psa_key_derivation_step_t step, argument
7117 switch (step) {
7128 return psa_tls12_prf_input(prf, step, data, data_length);
7138 psa_key_derivation_step_t step, argument
7143 step != PSA_KEY_DERIVATION_INPUT_SECRET) {
7162 psa_key_derivation_step_t step, argument
[all …]
Dpsa_crypto_pake.h75 psa_crypto_driver_pake_step_t step,
113 psa_crypto_driver_pake_step_t step,
Dpsa_crypto_driver_wrappers.h3242 psa_crypto_driver_pake_step_t step, in psa_driver_wrapper_pake_output() argument
3251 return( mbedtls_psa_pake_output( &operation->data.ctx.mbedtls_ctx, step, in psa_driver_wrapper_pake_output()
3260 step, output, output_size, output_length ) ); in psa_driver_wrapper_pake_output()
3264 (void) step; in psa_driver_wrapper_pake_output()
3274 psa_crypto_driver_pake_step_t step, in psa_driver_wrapper_pake_input() argument
3283 step, input, in psa_driver_wrapper_pake_input()
3292 step, in psa_driver_wrapper_pake_input()
3297 (void) step; in psa_driver_wrapper_pake_input()
Dssl_tls.c9032 for (psa_pake_step_t step = PSA_PAKE_STEP_KEY_SHARE; in mbedtls_psa_ecjpake_read_round() local
9033 step <= PSA_PAKE_STEP_ZK_PROOF; in mbedtls_psa_ecjpake_read_round()
9034 ++step) { in mbedtls_psa_ecjpake_read_round()
9043 status = psa_pake_input(pake_ctx, step, in mbedtls_psa_ecjpake_read_round()
9076 for (psa_pake_step_t step = PSA_PAKE_STEP_KEY_SHARE; in mbedtls_psa_ecjpake_write_round() local
9077 step <= PSA_PAKE_STEP_ZK_PROOF; in mbedtls_psa_ecjpake_write_round()
9078 ++step) { in mbedtls_psa_ecjpake_write_round()
9083 status = psa_pake_output(pake_ctx, step, in mbedtls_psa_ecjpake_write_round()
/mbedtls-latest/tests/src/drivers/
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-latest/tests/src/
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-latest/docs/architecture/
Dpsa-storage-resilience.md65 … the same between the end of step 1 and the end of step 3, since the core must behave differently …
74 …related to the key identifier _A_ used by the application interface. This step must not modify the…
82 * Before step 3: the system state has not changed at all. As far as the world is concerned, the key…
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.
95 * Before step 1: the system state has not changed at all. As far as the world is concerned, the key…
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.
238 1. Load the driver key identifier from the key file. If the key file does not exist, skip to step 4.
268 …cure-elements), under the simplifying assumption that each storage update step, as well as the rec…
[all …]
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-latest/tests/include/test/drivers/
Dpake.h56 psa_crypto_driver_pake_step_t step,
63 psa_crypto_driver_pake_step_t step,
/mbedtls-latest/tests/include/test/
Dhelpers.h76 unsigned long step; member
241 void mbedtls_test_set_step(unsigned long step);
/mbedtls-latest/include/psa/
Dcrypto.h3386 psa_key_derivation_step_t step,
3429 psa_key_derivation_step_t step,
3497 psa_key_derivation_step_t step,
3565 psa_key_derivation_step_t step,
Dcrypto_extra.h1480 psa_pake_step_t step,
1535 psa_pake_step_t step,
1845 psa_pake_step_t MBEDTLS_PRIVATE(step);
/mbedtls-latest/docs/architecture/psa-migration/
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-latest/docs/proposed/
Dpsa-driver-interface.md240 The entry points that implement each step of a multi-part operation are grouped into a family. A dr…
258 …ain any embedded pointers (except pointers to global data that do not change after the setup step).
317 …ion operation to a driver based on the location associated with the input step `PSA_KEY_DERIVATION…
319 1. If this step is passed via `psa_key_derivation_input_key()` for a key in a secure element:
366 psa_key_derivation_step_t step);
369 The function `psa_crypto_driver_key_derivation_get_input_type()` determines whether a given step is…
371 * `PSA_KEY_DERIVATION_INPUT_TYPE_INVALID`: the step is invalid for the algorithm of the operation t…
372 * `PSA_KEY_DERIVATION_INPUT_TYPE_OMITTED`: the step is optional for the algorithm of the operation …
373 * `PSA_KEY_DERIVATION_INPUT_TYPE_BYTES`: the step is valid and present and is a transparent byte st…
374 * `PSA_KEY_DERIVATION_INPUT_TYPE_KEY`: the step is valid and present and is a byte string passed vi…
[all …]
/mbedtls-latest/scripts/data_files/driver_templates/
Dpsa_crypto_driver_wrappers.h.jinja2748 psa_crypto_driver_pake_step_t step,
2757 return( mbedtls_psa_pake_output( &operation->data.ctx.mbedtls_ctx, step,
2766 step, output, output_size, output_length ) );
2770 (void) step;
2780 psa_crypto_driver_pake_step_t step,
2789 step, input,
2798 step,
2803 (void) step;
/mbedtls-latest/docs/architecture/psa-thread-safety/
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-latest/docs/
Dpsa-transition.md352 2. Call one of the key creation functions, passing the attributes defined in the previous step, to …
378 …up__cipher/#group__cipher_1ga9caddac1a429a5032d6d4a907fb70ba1). Skip this step with ECB since it d…
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 …
[all …]
Dpsa-driver-example-and-guide.md16 …step (one function call), such as verifying a signature, are called *Single-Part Operations*. On t…

12