Use uniform signatures in Crypto service
Closed, ResolvedPublic

Description

This task is to amend the existing Crypto service to use the uniform signature features made available by the TF-M framework. As part of this task, provide a refactoring of the tests to make sure both S and NS interfaces are verified with the same level of coverage during Regression.

adeaarm created this task.Thu, Mar 28, 1:58 PM
adeaarm triaged this task as Normal priority.
adeaarm updated the task description. (Show Details)
adeaarm added a comment.EditedThu, Mar 28, 2:09 PM

The changes that complete this task are available here:

https://review.trustedfirmware.org/c/trusted-firmware-m/+/747/ (to do a minor clean up in the autogenerated veneers template files)
https://review.trustedfirmware.org/c/trusted-firmware-m/+/748 (to amend the Crypto service to use uniform signatures, and use the psa_status_t consistently throughout all the internal APIs)
https://review.trustedfirmware.org/c/trusted-firmware-m/+/783 (the tests are refactored so that both S and NS suites run the same verification, i.e. they verify the same interfaces, but respectively from NS and S)

adeaarm updated the task description. (Show Details)Fri, Mar 29, 4:23 PM
adeaarm closed this task as Resolved.Sat, Apr 13, 12:20 AM