Lines Matching refs:location

25 … secure enclave, etc. An opaque driver is invoked for the specific [key location](#lifetimes-and-l…
39 [Req.location] Applications can tell which location values correspond to which secure element drive…
79 … of headers is empty. The header files must be present at the specified location relative to a dir…
84 * `"location"` (not permitted for transparent drivers, optional for opaque drivers, integer or stri…
112 …* either the key is transparent (its location is `PSA_KEY_LOCATION_LOCAL_STORAGE`) and the driver …
113 … is opaque (its location is not `PSA_KEY_LOCATION_LOCAL_STORAGE`) and the driver is an opaque driv…
125 If multiple opaque drivers have the same location, the list of driver specifications is invalid.
317 The core decides whether to dispatch a key derivation operation to a driver based on the location a…
595 The core decides whether to dispatch a PAKE operation to a driver based on the location of the prov…
598 1. If the location of the `password` is the local storage
601 2. If the location of the `password` is the location of a secure element
1100 …y()`, or by `psa_copy_key()` when copying a key from or to a different [location](#lifetimes-and-l…
1102 …y"`: called by `psa_import_key()`, or by `psa_copy_key()` when copying a key from another location.
1105 * `"copy_key"`: called by `psa_copy_key()` when copying a key within the same [location](#lifetimes…
1110 …_derivation_output_key()` or `psa_copy_key()` before creating a key in the location of this driver.
1241 A built-in key is identified by its location and its **slot number**. Drivers that support built-in…
1253 …location at which the driver was declared and a persistence level with which the platform is attem…
1276 …s assigned a [location](#lifetimes-and-locations). The driver is invoked for all actions that use …
1278 …ey which is only accessible inside the secure element designated by the location `PSA_KEY_LOCATION…
1301 …location. Keys in the default location (`PSA_KEY_LOCATION_LOCAL_STORAGE = 0`) are transparent: the…
1305 …location called `PSA_KEY_LOCATION_`*prefix* where *prefix* is the value of the `"prefix"` property…
1347 #### Driver location values
1349 How does a driver author decide which location values to use? It should be possible to combine driv…
1351 …enerate distinct location values as needed? This can be convenient, but it's also risky: if you up…
1353 The current plan is for Arm to maintain a registry of vendors and assign a location namespace to ea…