From 41ac513de8a28b2b7fd0d0b98be84cba50be2d98 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Wed, 9 Jan 2019 16:13:42 +0100 Subject: [PATCH] Don't use key derivation multipart inputs for key agreement It isn't a good fit. It's overly complex for what the API can do now, which is Diffie-Hellman. Consider it again later for more complex use cases such as authenticated key exchanges. --- include/psa/crypto_values.h | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/include/psa/crypto_values.h b/include/psa/crypto_values.h index fedd35c5c5..c799081d85 100644 --- a/include/psa/crypto_values.h +++ b/include/psa/crypto_values.h @@ -1454,21 +1454,6 @@ */ #define PSA_KDF_STEP_INFO ((psa_key_derivation_step_t)0x0203) -/** The private key in a key agreement. - * - * This must be a key pair of the appropriate type for the key agreement - * algorithm. - */ -#define PSA_KDF_STEP_OUR_KEY ((psa_key_derivation_step_t)0x0301) - -/** A label for key derivation. - * - * This may be a key pair of the appropriate type for the key agreement - * algorithm, or a direct input which is parsed as a public key in the - * same format as psa_import_key(). - */ -#define PSA_KDF_STEP_PEER_KEY ((psa_key_derivation_step_t)0x0302) - /**@}*/ #endif /* PSA_CRYPTO_VALUES_H */