- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have read from https://www.intel.com/content/dam/develop/external/us/en/documents/overview-signing-whitelisting-intel-sgx-enclaves.pdf that in release mode, an check is performed to see if the enclave signer is whitelisted.
However, when I try to build https://github.com/intel/linux-sgx/tree/master/SampleCode with `make SGX_DEBUG=0`, sign it with a random generated key from openssl and then run it, It runs without any error.
Why does the sample code still run when the key is not whitelisted?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Launch Policy List (previously known as the Whitelist) is only enforced/used when launching Windows enclaves. On Linux, any enclave is allowed to launch due to a newer feature called Flexible Launch Control.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Plzfgme,
This thread will no longer be monitored since we have provided information. If you need any additional information from Intel, please submit a new question.
Regards,
Aznie
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page