Open
Conversation
Draft
This file contains hidden or 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.
Changing the measurement from being hard-coded to the 3 required files (or previously, and like other Enclaves, memory-layout measurements) to flexible measurement composed of an unlimited number of file hashes.
Files can either be already present in the enclave (resident), or declared to have a certain hash but not yet there (absent).
Files can either be identity -- be a part of the sealing key because they are relevant to what the enclave is, or non-identity. This doesn't affect the attestation measurement, because attestation ensures that the exact desired state is honored by the untrusted host.
TODO:
Other PR's:
Future PR TODO's:
eappbinary to.ke, and a dynamic verifier.