From: Lukasz Pawelczyk Date: Fri, 17 Nov 2017 14:20:36 +0000 (+0100) Subject: Clarification for key_derive_dh, EC keys are also accepted X-Git-Tag: submit/tizen/20180315.113946~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d13ea7e43f5fec4d1930feca73141485abcbbd9d;p=platform%2Fcore%2Fsecurity%2Fyaca.git Clarification for key_derive_dh, EC keys are also accepted Change-Id: I763712bb97de47267ebd1303bc3718c573edb164 --- diff --git a/api/yaca/yaca_key.h b/api/yaca/yaca_key.h index bf871f6..4f82cd9 100644 --- a/api/yaca/yaca_key.h +++ b/api/yaca/yaca_key.h @@ -282,7 +282,7 @@ int yaca_key_extract_parameters(const yaca_key_h key, yaca_key_h *params); * @remarks The @a secret should not be used as a symmetric key. * To produce a symmetric key pass the secret to a key derivation function (KDF) * or a message digest function. - * @remarks Both the keys passed should be of DH type. + * @remarks Both the keys passed should be of DH or EC type. * @remarks The @a secret should be freed with yaca_free(). * @param[in] prv_key Our private key * @param[in] pub_key Peer public key