Page MenuHomePhabricator

Use uniform signatures in Crypto service
Closed, ResolvedPublic


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.

Event Timeline

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

The changes that complete this task are available here: (to do a minor clean up in the autogenerated veneers template files) (to amend the Crypto service to use uniform signatures, and use the psa_status_t consistently throughout all the internal APIs) (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)Mar 29 2019, 4:23 PM
adeaarm closed this task as Resolved.Apr 13 2019, 12:20 AM