Add the one-shot API tests to the existing multipart counterpart test. Highlight one-shot tests that should be added from scratch.
Description
Description
Event Timeline
Comment Actions
Hash: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10544
MAC: Support in mbedtls-2.26.0 for the single-shot APIs is not present. I have a patch to enable the tests and the shim layer in TF-M, I will keep it private until support from the backend side is available somehow for the feature-cc-psa-crypto-drivers dev branch.
Cipher: Support in mbedtls-2.26.0 for the single-shot APIs is not present. I have a patch to enable the tests and the shim layer in TF-M, I will keep it private until support from the backend side is available somehow for the feature-cc-psa-crypto-drivers dev branch.
AEAD: Single-shot APIs for AEAD are already supported, multipart is missing (both in TF-M and in the backend and driver entry points, still pending review in mbedTLS)
No Key agreement single shot API test yet. Need to understand and add it.
Comment Actions
Cipher/MAC single-shot APIs patches:
Only item left is Key-agreement investigation into usage of single-shot APIs
Comment Actions
Single shot key agreement:
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10867
Created a branch in tf-m-tests repo named feature-cc-psa-crypto-drivers to be able to push changes based on an development_2.x flow (rather than using the upgraded mbedtls 3.0 features)