Lines Matching refs:from
40 As a consequence, apart from the listed cases, the API calls inherit directly from the [resilience …
63 If the core loses power between steps 1 and 2, the key does not exist yet. This is fine from an app…
117 A key creation function must transform the internal storage from a state where file `id` does not e…
173 5. Remove the key from the transaction list.
177 * If the key exists in the secure element, just remove it from the transaction list.
178 … element, first remove the key file if it is present, then remove the key from the transaction lis…
185 4. Remove the key from the transaction list.
189 …y_key"` entry point, then remove the key file, and finally remote the key from the transaction lit…
190 … element, remove the key file if it is still present, then remove the key from the transaction lis…
202 5. Remove the key from the transaction list.
209 4. Remove the key from the transaction list.
215 3. Remove the key from the transaction list.
219 …nsaction list does not need to include the driver key identifier: it can be read from the key file.
227 5. Remove the key from the transaction list.
234 4. Remove the key from the transaction list.
238 1. Load the driver key identifier from the key file. If the key file does not exist, skip to step 4.
241 4. Remove the key from the transaction list.
246 * The flow of information is somewhat different from transparent keys and keys in stateless secure …
254 …might be in a transitional state, the core will request a key destruction from the driver. This me…
297 …nd test what happens if the library is updated on a device with leftovers from an interrupted tran…
322 …ist, then nothing needs to be done for recovery, other than removing `id` from the transaction lis…
325 …ecure element, and if it does, keep it and keep `id`. If not, remove `id` from the internal storag…
341 …ecure element, and if it does, keep it and keep `id`. If not, remove `id` from the internal storag…
363 3. Remove the key identifier from the transaction list.
386 …ist, then nothing needs to be done for recovery, other than removing `id` from the transaction lis…
399 1. Load the current list from the transaction list if it exists and it is not already cached in mem…
403 To remove a key identifier from the list:
406 2. Remove the key identifier from the array. If it wasn't the last element in array, move array ele…
415 3. Create the key file _A_ in the internal storage. Note that this is done at a different time from…
417 5. Remove _A_ [from the transaction list file](#transaction-list-file-manipulation).
423 * Remove the key from the transaction list.
435 3. Remove the key file _A_ from the internal storage.
436 4. Remove _A_ [from the transaction list file](#transaction-list-file-manipulation).
445 …ocation and the driver key identifier, although we could get the location from the transaction lis…
447 3. Remove the key file _A_ from the internal storage.
448 4. Remove _A_ [from the transaction list file](#transaction-list-file-manipulation).
463 * Version (2 bytes): 0x0003. (Chosen to differ from the first two bytes of a [dynamic secure elemen…
500 * When invoked from the test hook on a key file: on that key.
501 * When invoked from the test hook on the transaction file: on all the keys listed in the transactio…
502 * When invoked from a test secure element: on the specified key.