It was said in this forum that a launch enclave could potentially let any enclave run on the system:
In the SGX spec, Intel will need to provide an Intel-signed launch enclave to make SGX usable. This enclave will use EGETKEY to acquire the launch key for that processor and sign enclaves to allow them to run there. If that launch enclave isn't trying to enforce any particular policy about what enclaves can and can't run, it's actually a trivial piece of code. A basic launch enclave only requires user/enclave calling convention and an enclave CMAC implementation, both of which are simple and fundamental to any useful SGX implementation.
As the process of acquiring a production grade license is complex, I am looking for ways to test my code in non debug mode:
Thank you for your help!
#1. Is it possible to get such a Intel-signed launch enclave that will allow me to test my enclave code in a non-debug enclave? It is ok if it just runs on my machine.
#2. Is there another way, like an existing server that is publicly available, to run my enclave code in non debug mode?
Thank you for that answer.
My question was not regarding the attestation service, but regarding running the enclave in non-debug mode.
What is your answer in that case?
To debug enclave code, pls. note you do need to load the enclave in debug mode. If you load enclave in non-debug mode, you can’t set any breakpoint to enclave. You can find instruction how to load enclave in debug mode in the SGX SDK developer reference, I suppose you can find it in IDZ.
About your questions:
1. Is it possible to get such a Intel-signed launch enclave that will allow me to test my enclave code in a non-debug enclave? It is ok if it just runs on my machine.
No. There is an enclave launch white-list file, signed by Intel. I don’t think we can add arbitrary entry there.
2. Is there another way, like an existing server that is publicly available, to run my enclave code in non debug mode?