Andrew Thoelke
Andrew Thoelke
Clarify the way a 'volatile key' is designated, based on a lifetime persistence level of `PSA_KEY_PERSISTENCE_VOLATILE`. Ensure that this is consistent and clear throughout the specification. Fixes #262
Fixes #266
This follows the discussion in #242. I think I've captured the end state of that discussion, please review and let me know what I have missed. I still need to...
The sections of chapter 2 in the PQC extension do not refer directly to the relavent part of the Crypto API that they are to be used with. This might...
A design for the Firmware Update API to support SUIT for more advanced firmware update implementations was developed as an RFC (see [/design/rfc-01-fwu-suit](https://github.com/ARM-software/psa-api/blob/main/design/rfc-01-fwu-suit/rfc-01.rst)). The use cases, extension to the architecture...
## Use cases Some firmware update implementations want to duplicate the active firmware image into the memory used for staging a new firmware image. The following use cases have been...
* Add `psa_xof_operation_t` and its functions. * Add SHAKE128 and SHAKE256 XOF algorithms. Fixes #248
Change `mbedtls_svc_key_id_t` to `psa_key_id_t` in two function parameters introduced in version 1.3. Fixes #259
In some parts of the specification, 'volatile key' appears to mean a key with the default `PSA_KEY_LIFETIME_VOLATILE` (`0`) `lifetime` value. For example, * [9.3.1 Volatile keys](https://arm-software.github.io/psa-api/crypto/1.3/api/keys/lifetimes.html#volatile-keys) says: > Conceptually, a...
When defining the custom key generation and key derivation APIs, the content sourced from the MbedTLS experimental implementation of the API was not fully cleaned up for use as specification...