This repository was archived by the owner on May 9, 2022. It is now read-only.
feat(data enclave): save access key to auth enclave (WIP) #112
Conversation
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
PiDelport
added
feat
PiDelport
force-pushed
the
feat-data-enclave-save-access-key
branch
from
69f9528 to
0eaca55
Compare
…SealingError, SaveAccessKeyFailed
…_save_access_key_u
PiDelport
force-pushed
the
feat-data-service-auth-enclave-id
branch
from
118a927 to
4816cd8
Compare
PiDelport
force-pushed
the
feat-data-enclave-save-access-key
branch
from
0eaca55 to
17bb90f
Compare
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.
Still to do:
rtc_data_enclave::validate_and_save: construct theset_access_key::Requestproperly.rtc_uenclave/data-ocalls: implementrtc_save_access_key_u. In particular, figure out howdata_service_data_upload_okCloses issue Update the data-enclave's upload functionality to persist the upload access key and the using the authorization enclave #39
Follows PR feat(web service, data upload): pass the auth enclave ID to data enclave #111