Lines Matching refs:point

7 At this point, we are only concerned about one specific form of resilience: to a system crash or po…
15 …lls an API function, as far as the application is concerned, at any given point in time, the syste…
73 1. The core calls the driver's `"allocate_key"` entry point.
76 4. The core calls the driver's key creation entry point, passing it the driver's chosen identifier …
89 2. The core calls the driver's `"destroy_key"` entry point.
137 …nt). It may call the secure element driver's `"get_key_attributes"` entry point to find out whethe…
156 …point. Recovery means resuming the operation where it left off. For key creation, this means that …
158 …requires the secure element driver to have a `"get_key_attributes"` entry point. Compared to alway…
161 …point is potentially problematic because some secure elements don't have room to store key attribu…
167 …at will go in the key file before calling the driver's key creation entry point. Therefore the nor…
169 1. Call the driver's `"allocate_key"` entry point.
172 4. Call the driver's key creation entry point.
183 2. Call the driver's `"destroy_key"` entry point.
189 * If the key exists in the secure element, call the driver's `"destroy_key"` entry point, then remo…
198 1. Call the driver's `"allocate_key"` entry point.
200 3. Call the driver's key creation entry point.
208 3. Call the driver's `"destroy_key"` entry point.
211 …on list. This means following the destruction process, starting after the point where the key has …
214 2. Call the driver's `"destroy_key"` entry point, treating `DOES_NOT_EXIST` as a success.
223 1. Call the driver's `"allocate_key"` entry point.
226 4. Call the driver's key creation entry point.
232 2. Call the driver's `"destroy_key"` entry point.
236 …on list. This means following the destruction process, starting after the point where the key has …
239 2. Call the driver's `"destroy_key"` entry point, treating `DOES_NOT_EXIST` as a success.
252 …e about the state of the secure element. Merely calling a read-only entry point such as `"get_key_…
318 …t's key creation entry point, and key destruction must remove `id` after calling the secure elemen…
362 2. Call the secure element's key creation or destruction entry point.
369 …ernal storage in the internal storage before calling the secure element's key creation entry point.
370 * During key destruction, call the secure element's key destruction entry point before removing the…
372 … algorithm does not require the secure element driver to have a `"get_key_attributes"` entry point.
387 * If the file `id` exists, call the secure element's key destruction entry point (treating a `DOES_…
391 …secure-element-keys), i.e. secure elements with an `"allocate_key"` entry point. The design follow…
413 1. Call the driver's `"allocate_key"` entry point, obtaining the driver key identifier _D_ chosen b…
416 4. Call the secure element's key creation entry point.
421 …ecure element's key creation entry point has been called and succeeded, call the secure element's …
434 2. Call the secure element's `"destroy_key"` entry point.
446 2. Call the secure element's `"destroy_key"` entry point.