Li, Xun
d10cabebb5
Added new APIs in sgx_uae_service.h and sgx_ukey_exchange.h to support ECDSA quote based remote attestation. The set of legacy APIs supports EPID only and the set of new APIs supports ECDSA quotes. Enhanced Edger8r with structure deep-copy feature. Fixed bugs. Signed-off-by: Li, Xun <xun.li@intel.com>
2.0 KiB
Intel(R) Software Guard Extensions Protected Code Loader (Intel(R) SGX PCL) for Linux* OS
Introduction
Intel(R) SGX PCL is intended to protect Intellectual Property (IP) within the code for Intel(R) SGX enclave applications running on the Linux* OS.
Problem: Intel(R) SGX provides integrity of code and confidentiality and integrity of data at run-time. However, it does NOT provide confidentiality of code offline as a binary file on disk. Adversaries can reverse engineer the binary enclave shared object.
Solution: The enclave shared object (.so) is encrypted at build time. It is decrypted at enclave load time.
Intel(R) SGX PCL provides:
-
sgx_encrypt: A tool to encrypt the shared object at build time.
See sources at sdk\encrypt_enclave.
-
libsgx_pcl.a: A library that is statically linked to the enclave and enables the decryption of the enclave at load time.
See sources at sdk\protected_code_loader.
-
SampleEnclavePCL: Sample code which demonstrates how the tool and lib need to be integrated into an existing enclave project.
Purpose of this code sample:
Enclave writers should compare SampleEnclave and SampleEnclavePCL. This demonstrates how the Intel(R) SGX PCL is to be integrated into the project of the enclave writer.
Build and test the Intel(R) SGX PCL with the sample code
- To compile and run the sample
$ cd SampleEnclavePCL
$ make
$ ./app
Launch token initialization
If using libsgx-enclave-common or sgxpsw under version 2.4, an initialized variable launch_token needs to be passed as the 3rd parameter of API sgx_create_enclave. For example,
sgx_launch_token_t launch_token = {0}; sgx_create_enclave(ENCLAVE_FILENAME, SGX_DEBUG_FLAG, launch_token, NULL, &global_eid, NULL);