Lines Matching refs:not
15 …iven point in time, the system is either in a state where the function has not started yet, or in …
17 …rformed. For example, there will never be a situation where $M_2$ has been performed but not $M_1$.
19 The committing property is important not only for sequences of operations, but also when reporting …
26 * `remove()` removes a file (returning a specific error code if the file does not exist).
30 …of a file is always a version that was previously passed to `set()`. We do not try to handle the c…
34 …not have its own key store: in this case, the core stores a wrapped (i.e. encrypted) copy of the k…
40 …n-the-underlying-file-storage). We do not need to take any special precautions in the library desi…
63 …not exist yet. This is fine from an application's perspective since the core has not committed to …
74 …o the key identifier _A_ used by the application interface. This step must not modify the state of…
82 * Before step 3: the system state has not changed at all. As far as the world is concerned, the key…
83 … the core needs to find out whether the secure element completed step 5 or not, and reconcile the …
95 * Before step 1: the system state has not changed at all. As far as the world is concerned, the key…
96 … the core needs to find out whether the secure element completed step 3 or not, and reconcile the …
101 …ction assumes that the driver does not update its persistent state during a key management operati…
105 … for the normal case. Transaction recovery needs to be practical, but does not have to be fully op…
111 The PSA ITS API does not support enumerating files in storage: an ITS call can only access one file…
117 A key creation function must transform the internal storage from a state where file `id` does not e…
119 For a key that is not in a stateful element, the transaction consists of a single write operation. …
121 …use there is no way to enumerate all keys (and even if there was, it would not be practical). Ther…
129 … storage. Since we want to minimize the number of storage updates, we will not explore designs tha…
139 * Key creation, key not present in the secure element:
143 …f the core's persistent state, as would have been done if the transaction had not been interrupted.
145 * Key destruction, key not present in the secure element:
146 …he core's persistent state, as would have been done if the transaction had not been interrupted, b…
149 …he core's persistent state, as would have been done if the transaction had not been interrupted, b…
157 …not require querying the state of the secure element. This does not require any special precaution…
158 …dvantage if a key creation is interrupted. These do not seem like decisive advantages, so we will …
165 …r, the key lifetime (or at least the location), the driver key identifier (not constant-size), and…
178 * If the key does not exist in the secure element, first remove the key file if it is present, then…
190 * If the key does not exist in the secure element, remove the key file if it is still present, then…
194 …er, the key lifetime (or at least the location), and the driver key identifier (not constant-size).
196 For key creation, we do not need to store the key's metadata until it has been created in the secur…
211 …ransaction list, and ignoring any failure of a removal action if the item to remove does not exist:
219 …ts if the key exists in the secure element, then the transaction list does not need to include the…
236 …ransaction list, and ignoring any failure of a removal action if the item to remove does not exist:
238 1. Load the driver key identifier from the key file. If the key file does not exist, skip to step 4.
252 …Merely calling a read-only entry point such as `"get_key_attributes"` does not provide enough info…
266 …cation, there may or may not be a restart, and after that different state modifications may occur,…
295 …overy is itself an operation that must respect the invariant, and so we do not need any special te…
301 …red in a transaction list file. The name of the transaction list file does not depend on the ident…
303 …not exist, or is empty. The empty case must be supported because this is the initial state of the …
305 …t. If the transaction list does not contain the driver key identifier, and the key file does not e…
307 …s key identifier (as well as the location of the secure element if this is not encoded in the name…
313 …d` does not exist, then no resources corresponding to that key are in a secure element. This holds…
314 * If `id` is not in the transaction list and the file `id` exists and references a key in a statefu…
316 If `id` is in the transaction list and the file `id` exists, the key may or may not be present in t…
322 * If the file `id` does not exist, then nothing needs to be done for recovery, other than removing …
325 …ey exists in the secure element, and if it does, keep it and keep `id`. If not, remove `id` from t…
331 * If `id` is not in the transaction list and the file `id` does not exist, then no resources corres…
332 * If `id` is not in the transaction list and the file `id` exists, then the key is present in the s…
338 * If the file `id` does not exist, then destroy the key in the secure element (treating a `DOES_NOT…
341 …ey exists in the secure element, and if it does, keep it and keep `id`. If not, remove `id` from t…
367 …n list: a simple array of key identifiers. Since the transaction list does not contain the driver …
372 This choice of algorithm does not require the secure element driver to have a `"get_key_attributes"…
378 …d` does not exist, then no resources corresponding to that key are in a secure element. This holds…
379 * If `id` is not in the transaction list and the file `id` exists and references a key in a statefu…
386 * If the file `id` does not exist, then nothing needs to be done for recovery, other than removing …
399 1. Load the current list from the transaction list if it exists and it is not already cached in mem…
405 1. Load the current list if it is not already cached in memory. It is an error if the file does not…
468 …not critical for efficiency. Therefore, in addition to the key identifier which is required, we ad…
482 …led with `MBEDTLS_PSA_CRYPTO_SE_C`). This is a deprecated feature that has not been fully implemen…
498 The storage invariant check cannot check all keys in storage, and does not need to (for example, it…
521 …pected keys exist, and that keys that are expected to have been destroyed by recovery do not exist.