mbed TLS v2.23.0: Key derivation and pseudorandom generation

mbed TLS v2.23.0

Macros | Typedefs | Functions
Key derivation and pseudorandom generation

## Macros
#define | PSA_KEY_DERIVATION_OPERATION_INIT {0, 0, 0, {0}}
#define | PSA_KEY_DERIVATION_UNLIMITED_CAPACITY ((size_t)(-1))

## Typedefs
typedef struct psa_key_derivation_s | psa_key_derivation_operation_t

## Functions
static psa_key_derivation_operation_t | psa_key_derivation_operation_init (void)
psa_status_t | psa_key_derivation_setup (psa_key_derivation_operation_t *operation, psa_algorithm_t alg)
psa_status_t | psa_key_derivation_get_capacity (const psa_key_derivation_operation_t *operation, size_t *capacity)
psa_status_t | psa_key_derivation_set_capacity (psa_key_derivation_operation_t *operation, size_t capacity)
psa_status_t | psa_key_derivation_input_bytes (psa_key_derivation_operation_t *operation, psa_key_derivation_step_t step, const uint8_t *data, size_t data_length)
psa_status_t | psa_key_derivation_input_key (psa_key_derivation_operation_t *operation, psa_key_derivation_step_t step, psa_key_handle_t handle)
psa_status_t | psa_key_derivation_key_agreement (psa_key_derivation_operation_t *operation, psa_key_derivation_step_t step, psa_key_handle_t private_key, const uint8_t *peer_key, size_t peer_key_length)
psa_status_t | psa_key_derivation_output_bytes (psa_key_derivation_operation_t *operation, uint8_t *output, size_t output_length)
psa_status_t | psa_key_derivation_output_key (const psa_key_attributes_t *attributes, psa_key_derivation_operation_t *operation, psa_key_handle_t *handle)
psa_status_t | psa_key_derivation_abort (psa_key_derivation_operation_t *operation)
psa_status_t | psa_raw_key_agreement (psa_algorithm_t alg, psa_key_handle_t private_key, const uint8_t *peer_key, size_t peer_key_length, uint8_t *output, size_t output_size, size_t *output_length)

## Detailed Description

## Macro Definition Documentation

## ◆ PSA_KEY_DERIVATION_OPERATION_INIT

#define PSA_KEY_DERIVATION_OPERATION_INIT {0, 0, 0, {0}}

This macro returns a suitable initializer for a key derivation operation object of type psa_key_derivation_operation_t.

Definition at line 273 of file crypto_struct.h.

## ◆ PSA_KEY_DERIVATION_UNLIMITED_CAPACITY

#define PSA_KEY_DERIVATION_UNLIMITED_CAPACITY ((size_t)(-1))

Use the maximum possible capacity for a key derivation operation.

Use this value as the capacity argument when setting up a key derivation to indicate that the operation should have the maximum possible capacity. The value of the maximum possible capacity depends on the key derivation algorithm.

Definition at line 3248 of file crypto.h.

## Typedef Documentation

## ◆ psa_key_derivation_operation_t

typedef struct psa_key_derivation_s psa_key_derivation_operation_t

The type of the state data structure for key derivation operations.

Before calling any function on a key derivation operation object, the application must initialize it by any of the following means:

- Set the structure to all-bits-zero, for example:
  psa_key_derivation_operation_t operation;
  memset(&operation, 0, sizeof(operation));
- Initialize the structure to logical zero values, for example:
  psa_key_derivation_operation_t operation = {0};
- Initialize the structure to the initializer PSA_KEY_DERIVATION_OPERATION_INIT, for example:
  psa_key_derivation_operation_t operation = PSA_KEY_DERIVATION_OPERATION_INIT;
- Assign the result of the function psa_key_derivation_operation_init() to the structure, for example:
  psa_key_derivation_operation_t operation;
  operation = psa_key_derivation_operation_init();

This is an implementation-defined `struct`. Applications should not make any assumptions about the content of this structure except as directed by the documentation of a specific implementation.

Definition at line 3061 of file crypto.h.

## Function Documentation

## ◆ psa_key_derivation_abort()

psa_status_t psa_key_derivation_abort | ( | psa_key_derivation_operation_t * | operation | ) |

Abort a key derivation operation.

Aborting an operation frees all associated resources except for the `operation` structure itself. Once aborted, the operation object can be reused for another operation by calling psa_key_derivation_setup() again.

This function may be called at any time after the operation object has been initialized as described in psa_key_derivation_operation_t.

In particular, it is valid to call psa_key_derivation_abort() twice, or to call psa_key_derivation_abort() on an operation that has not been set up.

Parameters

  [in,out] | operation | The operation to abort.

Return values

  PSA_SUCCESS |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_get_capacity()

psa_status_t psa_key_derivation_get_capacity | ( | const psa_key_derivation_operation_t * | operation,
|  | size_t * | capacity
| ) |  |

Retrieve the current capacity of a key derivation operation.

The capacity of a key derivation is the maximum number of bytes that it can return. When you get N bytes of output from a key derivation operation, this reduces its capacity by N.

Parameters

  [in] | operation | The operation to query.
  [out] | capacity | On success, the capacity of the operation.

Return values

  PSA_SUCCESS |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_BAD_STATE | The operation state is not valid (it must be active).
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_input_bytes()

psa_status_t psa_key_derivation_input_bytes | ( | psa_key_derivation_operation_t * | operation,
|  | psa_key_derivation_step_t | step,
|  | const uint8_t * | data,
|  | size_t | data_length
| ) |  |

Provide an input for key derivation or key agreement.

Which inputs are required and in what order depends on the algorithm. Refer to the documentation of each key derivation or key agreement algorithm for information.

This function passes direct inputs, which is usually correct for non-secret inputs. To pass a secret input, which should be in a key object, call psa_key_derivation_input_key() instead of this function. Refer to the documentation of individual step types (`PSA_KEY_DERIVATION_INPUT_xxx` values of type psa_key_derivation_step_t) for more information.

If this function returns an error status, the operation enters an error state and must be aborted by calling psa_key_derivation_abort().

Parameters

  [in,out] | operation | The key derivation operation object to use. It must have been set up with psa_key_derivation_setup() and must not have produced any output yet.
  | step | Which step the input data is for.
  [in] | data | Input data to use.
  | data_length | Size of the `data` buffer in bytes.

Return values

  PSA_SUCCESS | Success.
  PSA_ERROR_INVALID_ARGUMENT | `step` is not compatible with the operation's algorithm.
  PSA_ERROR_INVALID_ARGUMENT | `step` does not allow direct inputs.
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The operation state is not valid for this input `step`.
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_input_key()

psa_status_t psa_key_derivation_input_key | ( | psa_key_derivation_operation_t * | operation,
|  | psa_key_derivation_step_t | step,
|  | psa_key_handle_t | handle
| ) |  |

Provide an input for key derivation in the form of a key.

Which inputs are required and in what order depends on the algorithm. Refer to the documentation of each key derivation or key agreement algorithm for information.

This function obtains input from a key object, which is usually correct for secret inputs or for non-secret personalization strings kept in the key store. To pass a non-secret parameter which is not in the key store, call psa_key_derivation_input_bytes() instead of this function. Refer to the documentation of individual step types (`PSA_KEY_DERIVATION_INPUT_xxx` values of type psa_key_derivation_step_t) for more information.

If this function returns an error status, the operation enters an error state and must be aborted by calling psa_key_derivation_abort().

Parameters

  [in,out] | operation | The key derivation operation object to use. It must have been set up with psa_key_derivation_setup() and must not have produced any output yet.
  | step | Which step the input data is for.
  | handle | Handle to the key. It must have an appropriate type for `step` and must allow the usage PSA_KEY_USAGE_DERIVE.

Return values

  PSA_SUCCESS | Success.
  PSA_ERROR_INVALID_HANDLE |
  PSA_ERROR_NOT_PERMITTED |
  PSA_ERROR_INVALID_ARGUMENT | `step` is not compatible with the operation's algorithm.
  PSA_ERROR_INVALID_ARGUMENT | `step` does not allow key inputs of the given type or does not allow key inputs at all.
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The operation state is not valid for this input `step`.
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_key_agreement()

psa_status_t psa_key_derivation_key_agreement | ( | psa_key_derivation_operation_t * | operation,
|  | psa_key_derivation_step_t | step,
|  | psa_key_handle_t | private_key,
|  | const uint8_t * | peer_key,
|  | size_t | peer_key_length
| ) |  |

Perform a key agreement and use the shared secret as input to a key derivation.

A key agreement algorithm takes two inputs: a private key `private_key` a public key `peer_key`. The result of this function is passed as input to a key derivation. The output of this key derivation can be extracted by reading from the resulting operation to produce keys and other cryptographic material.

If this function returns an error status, the operation enters an error state and must be aborted by calling psa_key_derivation_abort().

Parameters

  [in,out] | operation | The key derivation operation object to use. It must have been set up with psa_key_derivation_setup() with a key agreement and derivation algorithm `alg` (`PSA_ALG_XXX` value such that PSA_ALG_IS_KEY_AGREEMENT(`alg`) is true and PSA_ALG_IS_RAW_KEY_AGREEMENT(`alg`) is false). The operation must be ready for an input of the type given by `step`.
  | step | Which step the input data is for.
  | private_key | Handle to the private key to use.
  [in] | peer_key | Public key of the peer. The peer key must be in the same format that psa_import_key() accepts for the public key type corresponding to the type of private_key. That is, this function performs the equivalent of psa_import_key(..., `peer_key`, `peer_key_length`) where with key attributes indicating the public key type corresponding to the type of `private_key`. For example, for EC keys, this means that peer_key is interpreted as a point on the curve that the private key is on. The standard formats for public keys are documented in the documentation of psa_export_public_key().
  | peer_key_length | Size of `peer_key` in bytes.

Return values

  PSA_SUCCESS | Success.
  PSA_ERROR_BAD_STATE | The operation state is not valid for this key agreement `step`.
  PSA_ERROR_INVALID_HANDLE |
  PSA_ERROR_NOT_PERMITTED |
  PSA_ERROR_INVALID_ARGUMENT | `private_key` is not compatible with `alg`, or `peer_key` is not valid for `alg` or not compatible with `private_key`.
  PSA_ERROR_NOT_SUPPORTED | `alg` is not supported or is not a key derivation algorithm.
  PSA_ERROR_INVALID_ARGUMENT | `step` does not allow an input resulting from a key agreement.
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_operation_init()

static psa_key_derivation_operation_t psa_key_derivation_operation_init | ( | void |  | ) |
| static

Return an initial value for a key derivation operation object.

## ◆ psa_key_derivation_output_bytes()

psa_status_t psa_key_derivation_output_bytes | ( | psa_key_derivation_operation_t * | operation,
|  | uint8_t * | output,
|  | size_t | output_length
| ) |  |

Read some data from a key derivation operation.

This function calculates output bytes from a key derivation algorithm and return those bytes. If you view the key derivation's output as a stream of bytes, this function destructively reads the requested number of bytes from the stream. The operation's capacity decreases by the number of bytes read.

If this function returns an error status other than PSA_ERROR_INSUFFICIENT_DATA, the operation enters an error state and must be aborted by calling psa_key_derivation_abort().

Parameters

  [in,out] | operation | The key derivation operation object to read from.
  [out] | output | Buffer where the output will be written.
  | output_length | Number of bytes to output.

Return values

  PSA_SUCCESS |
  PSA_ERROR_INSUFFICIENT_DATA | The operation's capacity was less than `output_length` bytes. Note that in this case, no output is written to the output buffer. The operation's capacity is set to 0, thus subsequent calls to this function will not succeed, even with a smaller output buffer.
  PSA_ERROR_BAD_STATE | The operation state is not valid (it must be active and completed all required input steps).
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_output_key()

psa_status_t psa_key_derivation_output_key | ( | const psa_key_attributes_t * | attributes,
|  | psa_key_derivation_operation_t * | operation,
|  | psa_key_handle_t * | handle
| ) |  |

Derive a key from an ongoing key derivation operation.

This function calculates output bytes from a key derivation algorithm and uses those bytes to generate a key deterministically. The key's location, usage policy, type and size are taken from `attributes`.

If you view the key derivation's output as a stream of bytes, this function destructively reads as many bytes as required from the stream. The operation's capacity decreases by the number of bytes read.

If this function returns an error status other than PSA_ERROR_INSUFFICIENT_DATA, the operation enters an error state and must be aborted by calling psa_key_derivation_abort().

How much output is produced and consumed from the operation, and how the key is derived, depends on the key type:

- For key types for which the key is an arbitrary sequence of bytes of a given size, this function is functionally equivalent to calling psa_key_derivation_output_bytes and passing the resulting output to psa_import_key. However, this function has a security benefit: if the implementation provides an isolation boundary then the key material is not exposed outside the isolation boundary. As a consequence, for these key types, this function always consumes exactly (`bits` / 8) bytes from the operation. The following key types defined in this specification follow this scheme:
  - PSA_KEY_TYPE_AES;
  - PSA_KEY_TYPE_ARC4;
  - PSA_KEY_TYPE_CAMELLIA;
  - PSA_KEY_TYPE_DERIVE;
  - PSA_KEY_TYPE_HMAC.
- For ECC keys on a Montgomery elliptic curve (PSA_KEY_TYPE_ECC_KEY_PAIR(`curve`) where `curve` designates a Montgomery curve), this function always draws a byte string whose length is determined by the curve, and sets the mandatory bits accordingly. That is:
  - Curve25519 (PSA_ECC_CURVE_MONTGOMERY, 255 bits): draw a 32-byte string and process it as specified in RFC 7748 §5.
  - Curve448 (PSA_ECC_CURVE_MONTGOMERY, 448 bits): draw a 56-byte string and process it as specified in RFC 7748 §5.
- For key types for which the key is represented by a single sequence of `bits` bits with constraints as to which bit sequences are acceptable, this function draws a byte string of length (`bits` / 8) bytes rounded up to the nearest whole number of bytes. If the resulting byte string is acceptable, it becomes the key, otherwise the drawn bytes are discarded. This process is repeated until an acceptable byte string is drawn. The byte string drawn from the operation is interpreted as specified for the output produced by psa_export_key(). The following key types defined in this specification follow this scheme:
  - PSA_KEY_TYPE_DES. Force-set the parity bits, but discard forbidden weak keys. For 2-key and 3-key triple-DES, the three keys are generated successively (for example, for 3-key triple-DES, if the first 8 bytes specify a weak key and the next 8 bytes do not, discard the first 8 bytes, use the next 8 bytes as the first key, and continue reading output from the operation to derive the other two keys).
  - Finite-field Diffie-Hellman keys (PSA_KEY_TYPE_DH_KEY_PAIR(`group`) where `group` designates any Diffie-Hellman group) and ECC keys on a Weierstrass elliptic curve (PSA_KEY_TYPE_ECC_KEY_PAIR(`curve`) where `curve` designates a Weierstrass curve). For these key types, interpret the byte string as integer in big-endian order. Discard it if it is not in the range [0, N - 2] where N is the boundary of the private key domain (the prime p for Diffie-Hellman, the subprime q for DSA, or the order of the curve's base point for ECC). Add 1 to the resulting integer and use this as the private key x. This method allows compliance to NIST standards, specifically the methods titled "key-pair generation by testing candidates" in NIST SP 800-56A §5.6.1.1.4 for Diffie-Hellman, in FIPS 186-4 §B.1.2 for DSA, and in NIST SP 800-56A §5.6.1.2.2 or FIPS 186-4 §B.4.2 for elliptic curve keys.
- For other key types, including PSA_KEY_TYPE_RSA_KEY_PAIR, the way in which the operation output is consumed is implementation-defined.

In all cases, the data that is read is discarded from the operation. The operation's capacity is decreased by the number of bytes read.

For algorithms that take an input step PSA_KEY_DERIVATION_INPUT_SECRET, the input to that step must be provided with psa_key_derivation_input_key(). Future versions of this specification may include additional restrictions on the derived key based on the attributes and strength of the secret key.

Parameters

  [in] | attributes | The attributes for the new key.
  [in,out] | operation | The key derivation operation object to read from.
  [out] | handle | On success, a handle to the newly created key. `0` on failure.

Return values

  PSA_SUCCESS | Success. If the key is persistent, the key material and the key's metadata have been saved to persistent storage.
  PSA_ERROR_ALREADY_EXISTS | This is an attempt to create a persistent key, and there is already a persistent key with the given identifier.
  PSA_ERROR_INSUFFICIENT_DATA | There was not enough data to create the desired key. Note that in this case, no output is written to the output buffer. The operation's capacity is set to 0, thus subsequent calls to this function will not succeed, even with a smaller output buffer.
  PSA_ERROR_NOT_SUPPORTED | The key type or key size is not supported, either by the implementation in general or in this particular location.
  PSA_ERROR_INVALID_ARGUMENT | The provided key attributes are not valid for the operation.
  PSA_ERROR_NOT_PERMITTED | The PSA_KEY_DERIVATION_INPUT_SECRET input was not provided through a key.
  PSA_ERROR_BAD_STATE | The operation state is not valid (it must be active and completed all required input steps).
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_INSUFFICIENT_STORAGE |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_set_capacity()

psa_status_t psa_key_derivation_set_capacity | ( | psa_key_derivation_operation_t * | operation,
|  | size_t | capacity
| ) |  |

Set the maximum capacity of a key derivation operation.

The capacity of a key derivation operation is the maximum number of bytes that the key derivation operation can return from this point onwards.

Parameters

  [in,out] | operation | The key derivation operation object to modify.
  | capacity | The new capacity of the operation. It must be less or equal to the operation's current capacity.

Return values

  PSA_SUCCESS |
  PSA_ERROR_INVALID_ARGUMENT | `capacity` is larger than the operation's current capacity. In this case, the operation object remains valid and its capacity remains unchanged.
  PSA_ERROR_BAD_STATE | The operation state is not valid (it must be active).
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_key_derivation_setup()

psa_status_t psa_key_derivation_setup | ( | psa_key_derivation_operation_t * | operation,
|  | psa_algorithm_t | alg
| ) |  |

Set up a key derivation operation.

A key derivation algorithm takes some inputs and uses them to generate a byte stream in a deterministic way. This byte stream can be used to produce keys and other cryptographic material.

To derive a key:

1. Start with an initialized object of type psa_key_derivation_operation_t.
2. Call psa_key_derivation_setup() to select the algorithm.
3. Provide the inputs for the key derivation by calling psa_key_derivation_input_bytes() or psa_key_derivation_input_key() as appropriate. Which inputs are needed, in what order, and whether they may be keys and if so of what type depends on the algorithm.
4. Optionally set the operation's maximum capacity with psa_key_derivation_set_capacity(). You may do this before, in the middle of or after providing inputs. For some algorithms, this step is mandatory because the output depends on the maximum capacity.
5. To derive a key, call psa_key_derivation_output_key(). To derive a byte string for a different purpose, call psa_key_derivation_output_bytes(). Successive calls to these functions use successive output bytes calculated by the key derivation algorithm.
6. Clean up the key derivation operation object with psa_key_derivation_abort().

If this function returns an error, the key derivation operation object is not changed.

If an error occurs at any step after a call to psa_key_derivation_setup(), the operation will need to be reset by a call to psa_key_derivation_abort().

Implementations must reject an attempt to derive a key of size 0.

Parameters

  [in,out] | operation | The key derivation operation object to set up. It must have been initialized but not set up yet.
  | alg | The key derivation algorithm to compute (`PSA_ALG_XXX` value such that PSA_ALG_IS_KEY_DERIVATION(`alg`) is true).

Return values

  PSA_SUCCESS | Success.
  PSA_ERROR_INVALID_ARGUMENT | `alg` is not a key derivation algorithm.
  PSA_ERROR_NOT_SUPPORTED | `alg` is not supported or is not a key derivation algorithm.
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The operation state is not valid (it must be inactive).
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

## ◆ psa_raw_key_agreement()

psa_status_t psa_raw_key_agreement | ( | psa_algorithm_t | alg,
|  | psa_key_handle_t | private_key,
|  | const uint8_t * | peer_key,
|  | size_t | peer_key_length,
|  | uint8_t * | output,
|  | size_t | output_size,
|  | size_t * | output_length
| ) |  |

Perform a key agreement and return the raw shared secret.

Warning
  The raw result of a key agreement algorithm such as finite-field Diffie-Hellman or elliptic curve Diffie-Hellman has biases and should not be used directly as key material. It should instead be passed as input to a key derivation algorithm. To chain a key agreement with a key derivation, use psa_key_derivation_key_agreement() and other functions from the key derivation interface.

Parameters

  | alg | The key agreement algorithm to compute (`PSA_ALG_XXX` value such that PSA_ALG_IS_RAW_KEY_AGREEMENT(`alg`) is true).
  | private_key | Handle to the private key to use.
  [in] | peer_key | Public key of the peer. It must be in the same format that psa_import_key() accepts. The standard formats for public keys are documented in the documentation of psa_export_public_key().
  | peer_key_length | Size of `peer_key` in bytes.
  [out] | output | Buffer where the decrypted message is to be written.
  | output_size | Size of the `output` buffer in bytes.
  [out] | output_length | On success, the number of bytes that make up the returned output.

Return values

  PSA_SUCCESS | Success.
  PSA_ERROR_INVALID_HANDLE |
  PSA_ERROR_NOT_PERMITTED |
  PSA_ERROR_INVALID_ARGUMENT | `alg` is not a key agreement algorithm
  PSA_ERROR_INVALID_ARGUMENT | `private_key` is not compatible with `alg`, or `peer_key` is not valid for `alg` or not compatible with `private_key`.
  PSA_ERROR_BUFFER_TOO_SMALL | `output_size` is too small
  PSA_ERROR_NOT_SUPPORTED | `alg` is not a supported key agreement algorithm.
  PSA_ERROR_INSUFFICIENT_MEMORY |
  PSA_ERROR_COMMUNICATION_FAILURE |
  PSA_ERROR_HARDWARE_FAILURE |
  PSA_ERROR_CORRUPTION_DETECTED |
  PSA_ERROR_STORAGE_FAILURE |
  PSA_ERROR_BAD_STATE | The library has not been previously initialized by psa_crypto_init(). It is implementation-dependent whether a failure to initialize results in this error code.

psa_key_derivation_operation_init
static psa_key_derivation_operation_t psa_key_derivation_operation_init(void)
PSA_KEY_DERIVATION_OPERATION_INIT
#define PSA_KEY_DERIVATION_OPERATION_INIT
Definition: crypto_struct.h:272
psa_key_derivation_s
Definition: crypto_struct.h:256