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

Support for per-scheme trust anchors #137

Open
thomas-fossati opened this issue Apr 11, 2023 · 0 comments
Open

Support for per-scheme trust anchors #137

thomas-fossati opened this issue Apr 11, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@thomas-fossati
Copy link
Contributor

thomas-fossati commented Apr 11, 2023

Problem

At present, Veraison assumes the binding of a trust anchor / verification key to an attesting environment.

Some attestation schemes (e.g., AWS Nitro) rely on a global "per-scheme" trust anchor, which is the same irrespective of the attesting environment that produces the evidence.

It should be possible for trust anchors to be associated with just an attestation scheme.

Possible solution

The natural way to achieve this is by using CoTS.

Additional context

Note that this depends on veraison/corim#64

@thomas-fossati thomas-fossati added the enhancement New feature or request label Apr 11, 2023
@thomas-fossati thomas-fossati changed the title feature: Support for per-scheme trust anchors Apr 11, 2023
@setrofim setrofim self-assigned this May 8, 2024
@setrofim setrofim removed their assignment Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants