Pass handle parameter last on key creation #111
No reviewers
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!111
Loading…
Reference in a new issue
No description provided.
Delete branch "psa-handle-param-order"
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?
Change the order of parameters for
psa_import_keyandpsa_generate_derived_keyto pass the handle output parameter last. This makes the order consistent with the general convention in the library to put inputs before outputs. Other key handle creation functions (psa_open_key,psa_generate_random_key,psa_copy_key) already had the handle output parameter last.psa_generate_derived_keyin./docs/getting_started.mdthat needs updating.psa_imprt_keyin./docs/getting_started.mdthat needs updating.getting_started.mdis out of scope of the API document release. We'll update it in a batch later.CI failures on API branch are to do with building with crypto as a submodule and also TLS using PSA, both of which we don't care about at this point in development.