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

Endorsements are implicitly conditional on reference values. Which ones? #251

Open
deeglaze opened this issue Jul 17, 2024 · 0 comments
Open

Comments

@deeglaze
Copy link
Collaborator

An Endorsed Values triple declares additional measurements that are valid when a Target Environment has been verified against reference measurements.

There can be multiple reference measurements that are signed for a certain class-id. I don't expect reference measurements to be signed as limited to any specific instance. It doesn't seem correct to just accept anything from the authorized-by. The only interpretation that I can think of that could work is if the endorsement triple's environment is also associated with a reference-value-triple in the same CoMID, and that reference value has been added to the ACS.

The 1 environment to identify the reference values doesn't apply to the conditional-endorsement-triple now though, so I'm guessing those aren't implicitly conditional on the reference values? I'd really like if we could solidify the semantics by giving explicit transformations of triples in CoRIM to the relations that have more explicitly defined semantics?

Evidence is divided up into one or more ev relations where the condition ECT identifies the Attester from which Evidence was collected. If the Verifier maintains multiple Attester sessions, the Verifier session may be identified using an ECT.

Is this "Evidence is" meant to be "Endorsements are"? The ev relation is for endorsements.

Evidence information is mapped to an addition ECT that populates each of the ECT fields.

This seems more correct, but by saying addition instead of the ae relation doesn't match the use of relation in the previous sentence.

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

No branches or pull requests

1 participant