Lines Matching refs:step
240 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…
375 * `PSA_KEY_DERIVATION_INPUT_TYPE_INTEGER`: the step is valid and present and is an integer. Call `p…
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.
409 * `PSA_ERROR_DOES_NOT_EXIST`: the input step is valid for this particular algorithm, but it is not …
410 …of this input step. This is not a fatal error and the driver can, for example, subsequently call t…
430 …step may be fragmented into multiple calls of `psa_key_derivation_input_bytes()`, and the core may…
435 psa_key_derivation_step_t step,
608 * `"pake_output"` (mandatory): derive cryptographic material for the specified step and output it.
609 …ut"` (mandatory): provides cryptographic material in the format appropriate for the specified step.
691 psa_crypto_driver_pake_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,
724 * `step` computation step based on which driver should perform an action.
739 The core checks that `input_length` is not greater than `PSA_PAKE_INPUT_SIZE(alg, prim, step)` and
1152 If a failure occurs after the `"allocate_key"` step but before the call to the second driver entry …