Key gen #188
Open
Key gen #188
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
|
can you please add a description of the workflow? i.e. a sequence of steps that are taken during local attestation, and the functions that are called? the PR is a bit large, and this will help with understanding all the code that you've added. thanks! |
|
I wrote up a quick document about the steps and functions calls. I linked it in the original description, but here it is again for convenience: https://drive.google.com/file/d/1EtHdv1WbyuTk4r6OGGWCNuufK6MC6SnA/view?usp=sharing |
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.
The goal of this part is to allow Opaque enclaves to establish a shared, secret key that is not known to any untrusted party (i.e. clients, driver, etc.). This key will be used to encrypt the intermediate results in the Spark-generated DAG (with Opaque operators).
See https://drive.google.com/file/d/1EtHdv1WbyuTk4r6OGGWCNuufK6MC6SnA/view?usp=sharing
The pull requests should be done in the following order:
Key-get -> gRPC reEncryption -> gRPC ServiceProvider -> gRPC Python Files