Lines Matching refs:destroy

77 …ever possible to revert this commitment by giving the secure element the order to destroy the key.)
157 * Minimize the information processing: [always destroy the key](#exploring-the-always-destroy-strat…
158 …ement, this has the advantage of maximizing the chance that a command to destroy key material is e…
192 #### Exploring the always-destroy strategy
217 #### Always-destroy strategy with a simpler transaction file
219 We can modify the [always-destroy strategy](#exploring-the-always-destroy-strategy) to make the tra…
243 Compared with the basic always-destroy strategy:
254 This gives an advantage to the “always destroy” strategy. Under this strategy, if the key might be …
324 …* It is correct to destroy the key in the secure element (treating a `DOES_NOT_EXIST` error as a s…
338 * If the file `id` does not exist, then destroy the key in the secure element (treating a `DOES_NOT…
340 …* It is correct to destroy the key in the secure element (treating a `DOES_NOT_EXIST` error as a s…
384 …ers-with-recovery), we pick the [always-destroy recovery strategy with a simple transaction file](…
421 … creation entry point has been called and succeeded, call the secure element's destroy entry point.
439 If any step fails, remember the error but continue the process, to destroy the resources associated…
473     * 0: destroy key.