-
Notifications
You must be signed in to change notification settings - Fork 6
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
Modify aggregation workflows to support multiple enclave frameworks #31
Comments
As it has been decided to move towards "Enarx" from "Conclave" as confidential computing component, the primary things needed to be considered as below. |
"Wasmtime" needs to studied thoroughly to take advantage of Enarx platform & it's components. |
Moving toward "CCF" (https://github.com/microsoft/CCF) to investigate confidential computing part and resolve current use case problem. |
Enarx Updates: |
Apache Teaclave Updates:
|
Enarx Updates:
|
Is your feature request related to a problem? Please describe.
Support multiple enclave messaging frameworls
Describe the solution you'd like
Currently only R3 Conclave is supported for messaging and runtime for enclaves. We need to create a layer of abstraction over Conclave specific primitives within our workflows. This will allow us to plug into the enclave messaging layer and runtimes (Conclave, Anjuna).
Edit 23/06/2022
After research on several frameworks we have decieded to build the first non-Conclave integration with Anjuna.io
The text was updated successfully, but these errors were encountered: