You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.
After remote attestation is successful, the tenant must establish a secure communication channel with the enclave in order to provision secrets (i.e., the code to be run on Enarx). This is done through a DHKE. The public key for the enclave is:
generated inside the enclave
embedded in the Report Data portion of the enclave's Report, which is in turn embedded in the verified and signed Quote
Blocked by: mbedTLS modifications.
The text was updated successfully, but these errors were encountered:
After remote attestation is successful, the tenant must establish a secure communication channel with the enclave in order to provision secrets (i.e., the code to be run on Enarx). This is done through a DHKE. The public key for the enclave is:
generated inside the enclave
embedded in the Report Data portion of the enclave's Report, which is in turn embedded in the verified and signed Quote
Blocked by: mbedTLS modifications.
The text was updated successfully, but these errors were encountered: