yuzu-emu/mbedtls
1
0
Fork 0
mirror of https://github.com/yuzu-emu/mbedtls.git synced 2024-11-29 18:54:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Clarify the explanation of locations

Browse Source 
It's about who has access to the key material in plaintext, not directly
where the operation is performed.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
This commit is contained in:
Gilles Peskine 2020-12-11 18:46:01 +01:00
parent d0107b96af
commit 9b3e5a7b3e
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
include/psa/crypto_types.h
View File

@ -115,9 +115,8 @@ typedef uint32_t psa_algorithm_t;
* whether the key is _volatile_ or _persistent_. * whether the key is _volatile_ or _persistent_.
* See ::psa_key_persistence_t for more information. * See ::psa_key_persistence_t for more information.
* - Bits 8-31 (#PSA_KEY_LIFETIME_GET_LOCATION(\c lifetime)): * - Bits 8-31 (#PSA_KEY_LIFETIME_GET_LOCATION(\c lifetime)):
* location indicator. This value indicates where the key material is stored * location indicator. This value indicates which part of the system
* (or at least where it is accessible in cleartext) and where operations * has access to the key material and can perform operations using the key.
* on the key are performed.
* See ::psa_key_location_t for more information. * See ::psa_key_location_t for more information.
* *
* Volatile keys are automatically destroyed when the application instance * Volatile keys are automatically destroyed when the application instance
@ -176,9 +175,10 @@ typedef uint8_t psa_key_persistence_t;
* If an integration of Mbed TLS can make calls to external * If an integration of Mbed TLS can make calls to external
* cryptoprocessors such as secure elements, the location of a key * cryptoprocessors such as secure elements, the location of a key
* indicates which secure element performs the operations on the key. * indicates which secure element performs the operations on the key.
* Depending on the design of the driver for the secure element, the key * Depending on the design of the secure element, the key
* material may either be stored either in the secure element, or * material may either be stored either in the secure element, or
* in wrapped form alongside the key metadata in the primary local storage. * in wrapped (encrypted) form alongside the key metadata in the
* primary local storage.
* *
* This specification defines the following values of location indicators: * This specification defines the following values of location indicators:
* - \c 0: primary local storage. * - \c 0: primary local storage.