Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use v1.0.0 release of trusted services #763

Closed
wants to merge 5 commits into from
Closed

Conversation

gowthamsk-arm
Copy link
Contributor

The PR includes the following changes:

  1. Updates to docker files to use v1.0.0 of trusted services
  2. Configure the trusted service provider to use new RPC APIs
  3. Disable the key mappings test for the TS provider

Signed-off-by: Gowtham Suresh Kumar [email protected]

Builds and uses 1.0.0 version of trusted services in docker files.
Further commits updates the provider in parsec to use the new RPC
APIs.

Signed-off-by: Gowtham Suresh Kumar <[email protected]>
The newer version of trusted services repo also includes the
encoding scheme in the service name to locate the service.

Signed-off-by: Gowtham Suresh Kumar <[email protected]>
The 1.0.0 version of trusted services has RPC APIs changed. This
patch configures the provider to use the newer ones and updates
the submodule.

Signed-off-by: Gowtham Suresh Kumar <[email protected]>
The new libts library doesnt produce keys in the form of 00*.psa_its
so disable the tests in the CI for it.

Signed-off-by: Gowtham Suresh Kumar <[email protected]>
@gowthamsk-arm gowthamsk-arm force-pushed the trusted_services branch 4 times, most recently from 6a6ac18 to 67d5905 Compare May 9, 2024 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant