psa_key_derivation_input_bytes with LABEL or SALT #176
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto#176
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Version: psa-crypto-api-1.0-beta
API: psa_key_derivation_input_bytes with label/seed as step
Method:
Calling key derivation setup with alg such that PSA_ALG_IS_KEY_DERIVATION is true.
Then, calling psa_key_derivation_input_bytes with step as PSA_KEY_DERIVATION_INPUT_LABEL.
The return value is expected to be PSA_SUCCESS but the actual return value is PSA_ERROR_INVALID_ARGUMENT.
The same case with step as PSA_KEY_DERIVATION_INPUT_SEED
Issue request type
The permitted input depend on the algorithm. What algorithm did you pass to
psa_key_derivation_setup? Did it succeed? Which version did you use (there's no tagpsa-crypto-api-1.0-beta)?Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-830
@gilles-peskine-arm,
The spec version is psa-crypto-api-1.0-beta3
Below were the sequence of steps followed and the actual result
This is a question about the API. There may be a bug here, but we don't know yet.
This is expected: HKDF does not take a
LABELorSEEDinput (it takes an optionalSALT, then aSECRET, then anINFO).