7ebcbf34f9
The main purpose of psa_pake_get_key_share() is to provide a more straightforward and convenient call flow for regular PAKEs. Most PAKEs have a single key share and need a flow like this: op=PSA_PAKE_OPERATION_INIT; psa_pake_setup(); psa_pake_get_key_share(); psa_pake_set_key_share(); psa_pake_get_implicit_key(); Adding psa_pake_get/set_key_share() functions cuts out the psa_pake_data_t constants from the users vision, hiding complexity that exists only for unrelated PAKEs that aren't relevant for the user. This comes with the cost of the two additional API functions that we need to maintain. Since the current stream of work focuses on enabling J-PAKE, there are no benefits to these functions for now. Once algorithms that can benefit from this simplification are added, adding back these functions can be reconsidered. Signed-off-by: Janos Follath <janos.follath@arm.com> |
||
---|---|---|
.. | ||
crypto.h | ||
crypto_builtin_composites.h | ||
crypto_builtin_primitives.h | ||
crypto_compat.h | ||
crypto_config.h | ||
crypto_driver_common.h | ||
crypto_driver_contexts_composites.h | ||
crypto_driver_contexts_primitives.h | ||
crypto_extra.h | ||
crypto_platform.h | ||
crypto_se_driver.h | ||
crypto_sizes.h | ||
crypto_struct.h | ||
crypto_types.h | ||
crypto_values.h |