3 commits

Author	SHA1	Message	Date
Gilles Peskine	8817f61007	Use PSA_ASSERT(a) in preference to TEST_ASSERT(a==PSA_SUCCESS) ... This commit is the result of the following command, followed by reindenting (but not wrapping lines): perl -00 -i -pe 's/^( *)TEST_ASSERT\(([^;=]*)(?: |\n *)==\s*PSA_SUCCESS\s*\);$/${1}PSA_ASSERT($2 );/gm' tests/suites/test_suite_psa_*.function	2018-12-20 18:47:52 +01:00
Gilles Peskine	7bc9f68232	Convert the PSA crypto persistent storage tests to the new handle API ... Switch from the direct use of slot numbers to handles allocated by psa_allocate_key. The general principle for each function is: * Change `psa_key_slot_t slot` to `psa_key_handle_t handle` or `psa_key_id_t key_id` depending on whether it's used as a handle to an open slot or as a persistent name for a key. * Call psa_create_key() before using a slot, instead of calling psa_set_key_lifetime to make a slot persistent. Remove the unit test persistent_key_is_configurable which is no longer relevant.	2018-12-11 16:48:13 +01:00
Darryl Green	db2b8db715	psa: Add storage implementation for files ... Add new functions, psa_load_persistent_key(), psa_free_persistent_key_data(), and psa_save_persistent_key(), for managing persistent keys. These functions load to or save from our internal representation of key slots. Serialization is a concern of the storage backend implementation and doesn't abstraction-leak into the lifetime management code. An initial implementation for files is provided. Additional storage backends can implement this interface for other storage types.	2018-11-20 15:21:22 +00:00