Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gRPC python files #217

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

eric-feng-2011
Copy link
Contributor

@eric-feng-2011 eric-feng-2011 commented Apr 27, 2021

Python files for gRPC. Contains OpaqueClient and OpaqueRPCListener which are instrumental in gRPC and primary actors in steps 1, 2, 3, and 4 (really everything).

In gRPC, the workflow is as follows:

  1. RPCListener starts spark shell
  2. Client performs RA with the enclaves
  3. Client sends query to RPCListener
  4. RPCListener sends query to enclaves which executes it. The encrypted results (encrypted under enclave key) are saved in a file(s) on the RPCListener
  5. The client asks for post-verification
  6. The RPCListener performs post-verification and then re-encrypts the results under the SP key and then returns it
  7. The SP decrypts the encrypted values returned using its own key

This does NOT work alone. OpaqueClient for example uses several ServiceProvider functions that are only in another PR.

The pull requests should be done in the following order:
Key-get -> gRPC reEncryption -> gRPC ServiceProvider -> gRPC Python Files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant