You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior psa_key_derivation_output_key should be allowed if PSA_KEY_DERIVATION_INPUT_SECRET has been provided using psa_key_derivation_key_agreement.
Steps to reproduce
Follow the steps for key derivation as specified in the PSA spec, using psa_key_derivation_key_agreement as the input for step PSA_KEY_DERIVATION_INPUT_SECRET (this was done using psa-crypo as part of this PR).
The text was updated successfully, but these errors were encountered:
The documentation of the PSA_ERROR_NOT_PERMITTED case of psa_key_derivation_output_key is incomplete and inconsistent with the documentation of PSA_KEY_DERIVATION_INPUT_SECRET, which is correct. You can use it after a key agreement. This patch will be in version 1.0.1 of the PSA specification:
- The `PSA_KEY_DERIVATION_INPUT_SECRET` input was not provided through a key.
+ The `PSA_KEY_DERIVATION_INPUT_SECRET` input was neither provided through a key nor the result of a key agreement.
Description
mbed TLS build:
Version: latest commit ID: 0ca6d38
Expected behavior
psa_key_derivation_output_key
should be allowed ifPSA_KEY_DERIVATION_INPUT_SECRET
has been provided usingpsa_key_derivation_key_agreement
.Actual behavior
psa_key_derivation_output_key
fails withPSA_ERROR_NOT_PERMITTED
.can_output_key
is only set ifPSA_KEY_DERIVATION_INPUT_SECRET
is provided with a key.Steps to reproduce
Follow the steps for key derivation as specified in the PSA spec, using
psa_key_derivation_key_agreement
as the input for stepPSA_KEY_DERIVATION_INPUT_SECRET
(this was done usingpsa-crypo
as part of this PR).The text was updated successfully, but these errors were encountered: