Lines Matching refs:step
65 … the same between the end of step 1 and the end of step 3, since the core must behave differently …
74 …related to the key identifier _A_ used by the application interface. This step must not modify the…
82 * Before step 3: the system state has not changed at all. As far as the world is concerned, the key…
83 * Between step 3 and step 6: upon restart, the core needs to find out whether the secure element co…
84 * After step 6: the key has been created successfully.
95 * Before step 1: the system state has not changed at all. As far as the world is concerned, the key…
96 * Between step 1 and step 4: upon restart, the core needs to find out whether the secure element co…
97 * After step 4: the key has been destroyed successfully.
238 1. Load the driver key identifier from the key file. If the key file does not exist, skip to step 4.
268 …cure-elements), under the simplifying assumption that each storage update step, as well as the rec…
276 * Start transaction, restart, recovery step 1, restart, recovery step 1, recovery step 2.
277 * Start transaction, restart, recovery step 1, restart, recovery step 1, restart, recovery step 1, …
278 …saction, restart, recovery step 1, restart, recovery step 1, restart, recovery step 1, restart, re…
283 …step. For example, if we have confidence that recovery step 1 is idempotent (i.e. doing it twice i…
365 In addition, before or after step 2, create or remove the key file in the internal storage.
419 If any step fails:
439 If any step fails, remember the error but continue the process, to destroy the resources associated…