Update ckmc_import_wrapped_key description

The remark allows passing a wrapped key without any type letting the
backend autodetect it. Current implementation in SW backend does not
support it. In case of TZ backend such autodetection would unnecessarily
complicate the code.

Since the feature is not actually needed, the value CKMC_KEY_NONE option
will be forbidden from now on.

Change-Id: I2396d03bd28b0eeef0a1e922029808061beb71c8

diff --git a/src/include/ckmc/ckmc-manager.h b/src/include/ckmc/ckmc-manager.h
index 5e7a755..f4db37f 100644 (file)
--- a/src/include/ckmc/ckmc-manager.h
+++ b/src/include/ckmc/ckmc-manager.h
@@ -1108,8 +1108,7 @@ int ckmc_decrypt_data(ckmc_param_list_h params,
  *
  * @remarks The wrapping key must be either symmetric (#CKMC_KEY_AES) or private RSA
  *          (#CKMC_KEY_RSA_PRIVATE).
- * @remarks key_type in @a wrapped_key may be set to #CKMC_KEY_NONE as an input. In such case the
- *          key type is determined inside key manager during storing keys.
+ * @remarks key_type in @a wrapped_key must not be set to #CKMC_KEY_NONE.
  * @remarks password in @a wrapped_key must be set to NULL. There's no need to additionally encrypt
  *          a wrapped key.
  * @remarks If password in @a policy is provided, the stored key is additionally encrypted with it.