Remove driver-side enclave dependency #70
Merged
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.
Encryption (Utils.encryptInternalRowsFlatbuffers) now uses Java crypto on the
driver and an enclave on the workers, controlled by a flag.
Decryption is only called from the driver, so always uses Java crypto.
For sorting, the
FindRangeBounds
preprocessing task is shipped to a singleworker, where it uses the existing enclave implementation. (Thanks to András
Méhes.)
Fixes #64.