Lines Matching refs:inputs

310 * There are multiple inputs and outputs.
330 … to be called. This entry point provides the [initial inputs](#key-derivation-driver-initial-input…
331 …inputs, otherwise ignored): provide an extra input for the key derivation. This entry point is onl…
343 #### Key derivation driver initial inputs
345 The core conveys the initial inputs for a key derivation via an opaque data structure of type `psa_…
365     const psa_crypto_driver_key_derivation_inputs_t *inputs,
371 …NPUT_TYPE_INVALID`: the step is invalid for the algorithm of the operation that the inputs are for.
372 …ITTED`: the step is optional for the algorithm of the operation that the inputs are for, and has b…
373 …ake a copy of the input data (design note: [why a copy?](#key-derivation-inputs-and-buffer-ownersh…
379     const psa_crypto_driver_key_derivation_inputs_t *inputs,
383     const psa_crypto_driver_key_derivation_inputs_t *inputs,
387     const psa_crypto_driver_key_derivation_inputs_t *inputs,
392     const psa_crypto_driver_key_derivation_inputs_t *inputs,
399 * The first parameter `inputs` must be a pointer passed by the core to a key derivation driver setu…
409 … the initial inputs. This is not a fatal error. The driver will receive the input later as a [long…
421     const psa_crypto_driver_key_derivation_inputs_t *inputs);
426 * `inputs` is an opaque pointer to the [initial inputs](#key-derivation-driver-initial-inputs) for …
428 #### Key derivation driver long inputs
430 …inputs which it would not be practical to pass in the [initial inputs](#key-derivation-driver-init…
439 At the time of writing, no standard key derivation algorithm has long inputs. It is likely that suc…
592 …ing inputs and computation. Core side is responsible for keeping inputs and core set-data function…
596 When all inputs are collected and `"psa_pake_output"` or `"psa_pake_input"` is called for the first…
607 …atory): always the first entry point to be called. It is called when all inputs are collected and …
619 #### PAKE driver inputs
621 The core conveys the initial inputs for a PAKE operation via an opaque data structure of type `psa_…
631     const psa_crypto_driver_pake_inputs_t *inputs,
635     const psa_crypto_driver_pake_inputs_t *inputs,
639     const psa_crypto_driver_pake_inputs_t *inputs,
644     const psa_crypto_driver_pake_inputs_t *inputs,
648     const psa_crypto_driver_pake_inputs_t *inputs,
652     const psa_crypto_driver_pake_inputs_t *inputs,
656     const psa_crypto_driver_pake_inputs_t *inputs,
660     const psa_crypto_driver_pake_inputs_t *inputs,
665 The first parameter `inputs` must be a pointer passed by the core to a PAKE driver setup entry poin…
670 * `PSA_ERROR_BAD_STATE`: the inputs are not ready
677                               const psa_crypto_driver_pake_inputs_t *inputs );
681 * `inputs` is an opaque pointer to the [inputs](#pake-driver-inputs) for the PAKE operation.
683 The setup driver function should preserve the inputs using get-data functions.
921 …e sense that it always returns the same data when given the same entropy inputs) or non-determinis…
1371 #### Key derivation inputs and buffer ownership
1375 … own memory after the entry point returns. In the case of key derivation inputs, this could be rel…