Lines Matching refs:state

15 …state where the function has not started yet, or in a state where the function has returned. The a…
74 …fier _A_ used by the application interface. This step must not modify the state of the secure elem…
75 …t key identifier _A_ has the identifier _D_ in the driver, and that _A_ is in a half-created state.
78 6. The core updates the storage to indicate that _A_ is now in a fully created state. This conclude…
82 * Before step 3: the system state has not changed at all. As far as the world is concerned, the key…
83 … secure element completed step 5 or not, and reconcile the state of the storage with the state of …
95 * Before step 1: the system state has not changed at all. As far as the world is concerned, the key…
96 … secure element completed step 3 or not, and reconcile the state of the storage with the state of …
101 Note that the analysis in this section assumes that the driver does not update its persistent state…
117 …state where file `id` does not exist, to a state where file `id` exists and has its desired final …
119 …a stateful secure element because the state of the internal storage needs to change both before an…
121 …state of the secure element, there must be information in the internal storage that indicates that…
124 * Write the final state of `id`.
125 * Restore `t` to its initial state.
129 …state of `id` to be modified only once. In particular, if a key management involves writing an int…
140 …h will in general changing the key's driver identifier, which complicates state management in the …
143 …* Committing means finishing the update of the core's persistent state, as would have been done if…
146 …* Committing means finishing the update of the core's persistent state, as would have been done if…
149 …* Committing means finishing the update of the core's persistent state, as would have been done if…
156 * [Always follow the state of the secure element](#exploring-the-follow-the-secure-element-strategy…
157 …tions and commit all key destructions. This does not require querying the state of the secure elem…
158 …state of the secure element for key creation, but always go ahead with key destruction. This requi…
159 * Always abort key creation, but follow the state of the secure element for key destruction. I can'…
252 …ow if a transaction was in progress and the core cannot be sure about the state of the secure elem…
254 …roy” strategy. Under this strategy, if the key might be in a transitional state, the core will req…
264 …state, either in storage or in the (simulated) secure element, try both the nominal case and simul…
266 …tree of possibilities: after each state modification, there may or may not be a restart, and after…
268 …fication and no secure element access. The nominal case consists of three state modifications: sto…
289 * Normal operation must maintain a certain invariant on the state of the world (internal storage an…
295 * Testing of transaction recovery is independent of how the system state was reached. We only need …
303 …be supported because this is the initial state of the filesystem. When no transaction is in progre…
305 For the purposes of the state invariant, it matters whether the transaction list file contains the …
334 If `id` is in the transaction list, neither the state of `id` in the internal storage nor the state…
516 1. Create the initial state:
520 2. Call `psa_crypto_init()`. Expect success if the initial state satisfies the [storage invariant](…
522 4. Clean up the storage and the secure element test driver's state.