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
So far we have always been skipping the remote attestation process because we did not run the worker on an SGX-machine. Now that the SGX-infrastructure has been set up, we can actually do remote attestation. However, the current state of the worker does only allow IAS remote attestation, which needs an Intel licence. Obtaining a development licence is very easy quick and can be done here: https://api.portal.trustedservices.intel.com/EPID-attestation.
However, obtaining a production licence might take up to six months. Hence, we suggest using DCAP remote attestation, which simply needs an upgrade of the worker to upstream.
So far we have always been skipping the remote attestation process because we did not run the worker on an SGX-machine. Now that the SGX-infrastructure has been set up, we can actually do remote attestation. However, the current state of the worker does only allow IAS remote attestation, which needs an Intel licence. Obtaining a development licence is very easy quick and can be done here: https://api.portal.trustedservices.intel.com/EPID-attestation.
However, obtaining a production licence might take up to six months. Hence, we suggest using DCAP remote attestation, which simply needs an upgrade of the worker to upstream.
Blocked by
The text was updated successfully, but these errors were encountered: