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.

Sign up for GitHub

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

Jump to bottom

feature: evolving the OP-TEE Veraison TA #281

Open
thomas-fossati opened this issue Nov 21, 2024 · 0 comments
Open

feature: evolving the OP-TEE Veraison TA #281

thomas-fossati opened this issue Nov 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@thomas-fossati
Copy link
Contributor

thomas-fossati commented Nov 21, 2024 •
edited
Loading

As discussed in the context of OP-TEE/optee_os#7006 - specifically, in the following comments:

The (re)use of the PSA token format is not ideal.

I'd like to suggest we evolve the Veraison TA to implement a sample "Key Attestation" service, which stores private key material and exposes a sign API to its NW clients. The token format would be the one described in I-D.bft-rats-kat.

cc @mmxsrup
cc @hannestschofenig
@thomas-fossati thomas-fossati added the enhancement New feature or request label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thomas-fossati