You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: