I think constructing an "0-call enclaves" enclave can be implemented by using `sgx_no_tstd` instead of `sgx_tstd`. So feature gate `env` is not a way to use to construct an "0-call enclaves".
The current implementation is that environment variables are passed into the enclave from the normal world when the enclave is created, and there is no `ocall` to query and set environment variables while the enclave is running. Feature gate `env` can be used to control whether the enclave accepts environment variables from the normal world. When feature gate `env` is disabled, the enclave does not accept environment variables from the normal world, and the enclave can initialize custom trusted environment variables with method `initenv`. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/377#issuecomment-1084200763 You are receiving this because you are subscribed to this thread. Message ID: <apache/incubator-teaclave-sgx-sdk/pull/377/c1084200...@github.com>
