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
Since you have this "old-style" machine, I think what happens is that AESMD looks into its White List and fails to find your built gcc enclave (more particularly, fails to find MRSIGNER with which your gcc enclave is signed).
This is because SGX1 (with no FLC) uses a very restrictive policy for non-debug SGX enclaves. Since SGX2 (with FLC), the policy is more relaxed and allows to run non-debug SGX enclaves.
Anyway, my assumption is that your machine doesn't allow you to run non-debug enclaves. And in Gramine, enclaves are non-debug by default. So please add sgx.debug = true in your gcc.manifest.template file, rebuild and run again. Hopefully this solves your problem (AESMD will be satisfied with the debug enclave and let it run).
Issue:
gramine-sgx-get-token fails to connect to the AESMD service.
Steps to reproduce:
In the the /examples/gcc/ directory, run the command
SGX=1 make check
. This is also happening with other examples like curl.Expected result:
The regression tests should run.
Actual result:
Getting the following output:
It seems this is the same issue as this in the gsc repo.
Other related info:
sudo service aesmd status
:The text was updated successfully, but these errors were encountered: