This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
Cca: Get the evidence from EAR (EAT Attesation Result) #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chendave
changed the title
|
@Xynnn007 Is there any way for me to trigger the test again? or else can you help to rerun the test? thanks! |
I merged the csv fix. Just rebase the |
|
rebased, let's see whether the CI is happy now. |
CCA validation by the Verasion has some overlapping with the RVPS, the similar validation has been done by the Verasion already. So the validation of evidence in CoCo is not needed in theory. The parse of the CCA token here is to align with other verifier, e.g. TDX, and to support RVPS if that is the case of future planning. NOTE that each of the value we get from EAR is base64 encoded hex value. So, the reference value that are registered for RVPS are expected to be base64 encoded hex value as well. [1] https://datatracker.ietf.org/doc/draft-ietf-rats-ar4si/ Signed-off-by: Dave Chen <dave.chen@arm.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CCA validation by the Verasion has some overlapping with the RVPS, the similar validation has been done by the Verasion already. So the validation of evidence in CoCo is not needed in theory.
The parse of the CCA token here is to align with other verifier, e.g. TDX, and to support RVPS if that is the case of future planning.
NOTE that each of the value we get from EAR is base64 encoded hex value. So, the reference value that are registered for RVPS are expected to be base64 encoded hex value as well.
[1] https://datatracker.ietf.org/doc/draft-ietf-rats-ar4si/