Using the attestation generation capability of the new attestatation API inside the eservice enclave #502
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR depends on #501 and is meant to show how to use the attestation API within the eservice enclave to generate an attestation.
While the PR works with the current flow (with EPID attestations), a generous code refactoring (particularly of eservice and pservice) should be considered to remove EPID specific code (including the IAS client) -- possibly leaving only what is necessary to select the attestation to be produced.
This PR does not show how to use the attestation API for verification -- so the flow still uses the legacy code for EPID, particularly in the pservice and transaction processor in CCF.