Home
last modified time | relevance | path

Searched refs:destroy (Results 1 – 9 of 9) sorted by relevance

/openthread-3.6.0/third_party/mbedtls/repo/tests/suites/
Dtest_suite_psa_crypto_persistent_key.data39 Persistent key destroy
43 Persistent key destroy after restart
Dtest_suite_psa_crypto_slot_management.function47 * close it, destroy it, or do nothing;
165 * volatile key shouldn't invalidate/destroy it.
272 * Do something that wipes key data in volatile memory or destroy the
920 * that they have the expected value and destroy them. In that process,
1001 * expected value. Then, destroy it.
Dtest_suite_psa_crypto_se_driver_hal_mocks.function95 * MAX_KEY_ID_FOR_TEST. In addition, run the destroy function on key id
Dtest_suite_psa_crypto_se_driver_hal.function212 /* Null destroy: do nothing, but pretend it worked. */
1506 /* This time, destroy the key. */
Dtest_suite_pk.function185 /* test that freeing the context does not destroy the key */
Dtest_suite_psa_crypto.function600 goto destroy;
630 destroy:
/openthread-3.6.0/tests/scripts/thread-cert/
Dthread_cert.py130 node.destroy()
297 node.destroy()
Dnode.py75 self.destroy()
200 def destroy(self): member in OtbrDocker
737 def destroy(self): member in OtCli
/openthread-3.6.0/third_party/mbedtls/repo/docs/proposed/
Dpsa-driver-interface.md683 To destroy a key, the core simply destroys the wrapped key material, without invoking driver code.
717 To destroy a key, the core calls the driver's `"destroy_key"` entry point.
826 The core will pass authorized requests to destroy a built-in key to the [`"destroy_key"`](#key-mana…
856 …e key is stored and which application and system actions will create and destroy it. The lifetime …