Lines Matching refs:entry

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.
133 …s information will be stored in a persistent “transaction list”, with one entry per key. In this s…
137 … element). It may call the secure element driver's `"get_key_attributes"` entry point to find out …
156 …entry point. Recovery means resuming the operation where it left off. For key creation, this means…
158 … This requires the secure element driver to have a `"get_key_attributes"` entry point. Compared to…
161 …entry point is potentially problematic because some secure elements don't have room to store key a…
165 Each entry in the transaction list contains the API key identifier, the key lifetime (or at least t…
167 …ion that will go in the key file before calling the driver's key creation entry point. Therefore t…
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…
194 Each entry in the transaction list contains the API key identifier, the key lifetime (or at least t…
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.
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.
239 2. Call the driver's `"destroy_key"` entry point, treating `DOES_NOT_EXIST` as a success.
252 …be sure about the state of the secure element. Merely calling a read-only entry point such as `"ge…
318 …element's key creation entry point, and key destruction must remove `id` after calling the secure …
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 …t-for-secure-element-keys), i.e. secure elements with an `"allocate_key"` entry point. The design …
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 … the secure element's key creation entry point has been called and succeeded, call the secure elem…
434 2. Call the secure element's `"destroy_key"` entry point.
446 2. Call the secure element's `"destroy_key"` entry point.