mbedcrypto-3.0.1 doesn't have the support for persistent keys #382
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#382
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?
When running the PSA Crypto APIs tests from https://github.com/ARM-software/psa-arch-tests (Hash: e44ccebdff9631e2474d85650c1812d0ce001dc3) with TFM (Hash: 6e7be077eabef00b4825e245604148d82b11f832), there are tests couple of failures due to below reasons:
mbed-crypto used: (https://github.com/ARMmbed/mbed-crypto.git -b mbedcrypto-3.0.1)
The implementation of psa_open_key/psa_close_key requires the support for persistent key storage. Since mbedcrypto doesn't have support for storing persistent keys, psa_import_key fails for the same(Error: -134 - UNSUPPORTED). However, I'm not sure whether is mbedcrypto issue or TFM issue.
Test failures (Target- AN521):
TEST: 250 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_open_key 16 Byte AES
Failed at Checkpoint: 6
Actual: -134
Expected: 0
TEST RESULT: FAILED (Error Code=0x00000001)
TEST: 251 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_close_key 16 Byte AES
[Check 2] Test psa_close_key 24 Byte AES
Failed at Checkpoint: 3
Actual: -134
Expected: 0
TEST RESULT: FAILED (Error Code=0x00000001)
Please guide us on planning the support for persistent key storage.
Mbed Crypto does have persistent key storage. It works on top of the PSA ITS API. Mbed Crypto provides an implementation of PSA ITS over standard C stdio. It can also work with other PSA ITS implementations.
I can't speak to the TF-M integration.
@soby-mathew has confirmed that this is a TFM issue. Therefore, raised TFM issue - https://developer.trustedfirmware.org/T682