Unreadable storage and invalid data in storage should be different errors #332

Open
opened 2019-12-08 11:44:06 -06:00 by gilles-peskine-arm · 1 comment
gilles-peskine-arm commented 2019-12-08 11:44:06 -06:00 (Migrated from github.com)

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).

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).
ciarmcom commented 2019-12-08 15:33:47 -06:00 (Migrated from github.com)
*Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-1021*
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-ARMmbed/mbed-crypto#332
No description provided.