Unreadable storage and invalid data in storage should be different errors #332
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#332
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?
The PSA crypto specification defines a single error code that is applicable when reading storage:
PSA_ERROR_STORAGE_FAILURE, which is intended when the storage is unreadable or demonstrably corrupted. Reading invalid data from the storage when the storage subsystem thinks nothing is wrong should be a different error, typically indicating that data was saved with a different version or build of the PSA crypto implementation and cannot be read back with the present build (for example a key type or size that is not supported).Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-1021