Lines Matching refs:keys
14 …regardless of how the operations are performed. Under the hood, different keys may be stored and u…
24 * **Transparent** drivers implement cryptographic operations on keys that are provided in cleartext…
25 * **Opaque** drivers implement cryptographic operations on keys that can only be used inside a prot…
35 …celerators that operate on keys in cleartext; cryptoprocessors that can wrap keys with a built-in …
82 …, mandatory for opaque drivers): information about the [representation of keys](#key-format-for-op…
775 Additionally, opaque drivers can create keys through their [`"key_derivation_output_key"`](#key-der…
801 …ration functions are supposed to receive valid keys, and should not have to check and report inval…
805 …keys A and B (or more), then the creation of A must ensure that using it does not risk compromisin…
815 * For elliptic curve private keys (`PSA_KEY_TYPE_ECC_KEY_PAIR`), check the size and range. TODO: wh…
816 * For elliptic curve public keys (`PSA_KEY_TYPE_ECC_PUBLIC_KEY`), check the size and range, and tha…
875 To declare a cryptoprocessor can handle both cleartext and wrapped keys, you need to provide two dr…
881 …rypto/html/api/keys/management.html#c.psa_export_key) and [`psa_export_public_key()`](https://armm…
892 …volved when exporting, copying or destroying keys, or when importing, generating or deriving symme…
909 …on of [`psa_import_key()`](https://armmbed.github.io/mbed-crypto/html/api/keys/management.html#c.p…
912 …crypto/html/api/keys/management.html#c.psa_export_key) or [`psa_export_public_key()`](https://armm…
1033 * Some cryptoprocessors do not have persistent storage for individual keys. The representation of a…
1034 * Some cryptoprocessors have persistent storage for individual keys. The representation of a key is…
1050 …or [built-in keys](#built-in-keys). This allows drivers to efficiently represent application keys …
1106 …lled by functions that access a key to retrieve information about a [built-in key](#built-in-keys).
1159 …keys on behalf of multiple clients, and different clients may use the same key identifier to desig…
1166 TODO: some of the above doesn't apply to volatile keys
1237 #### Built-in keys
1239 Opaque drivers may declare built-in keys. Built-in keys can be accessed, but not created, through t…
1241 …ed by its location and its **slot number**. Drivers that support built-in keys must provide a `"ge…
1257 …-management-in-a-secure-element-with-storage). A driver may have built-in keys even if it doesn't …
1266 …n-a-secure-element-with-storage) entry point if there is one. If built-in keys must not be destroy…
1296 …1.0.0, defines [lifetimes](https://armmbed.github.io/mbed-crypto/html/api/keys/attributes.html?hig…
1301 … 0`) are transparent: the core has direct access to the key material. For keys in a location that …
1402 Should the entry point be called for symmetric keys as well?
1408 … For standard key types, this could plausibly be an issue for RSA private keys, where an implement…
1430 …orting intermediate material but can only import or randomly generate ECC keys. How does this driv…