Michał Kowalczyk
3d31f2d18d
This is the next part of the great loader rework, with a lot of breaking changes: - Complete removal of the "trusted children" thing - now children processes can be spawned arbitrarily and from arbitrary mountpoint types, without any additional configuration needed. - There's a new, required option in the manifest: `libos.entrypoint` - it specifies the URI to the entry binary in the first process. There's no need anymore to name the manifest and the first binary identically. - On SGX, the main binary is not measured in MRENCLAVE anymore - only PAL, LibOS and the manifest are measured. This is enough to bind MRENCLAVE to a specific entrypoint user executable if wanted - it just has to be mounted as a trusted file. - All Graphene SGX enclaves have now exactly the same MRENCLAVE. This is a hash of a "Graphene stub", which can "fork" into one of two states in runtime: initial process or child. The initial process creates a new "Graphene namespace" with a clean state, it can also be attested remotely (contrary to child processes). The initial process can spawn children processes by spawning a Graphene stub and directing it to start in the child mode. It then attests it locally, and if successful, establishes an encrypted pipe, "connects" to its own namespace and treats as trusted (including sending protected files key). - Now, there's only one, central manifest describing the initial state of a Graphene instance which can be spawned from it (previously, each process required a separate manifest which could have different configuration - which wasn't actually supported and didn't make sense design-wise). One downside of central manifests is that all processes require the same enclave configuration (e.g. size), but that was already the case so far because of broken checkpointing code. Also, this is only a temporary problem, which will cease to exist after the introduction of EDMM. - `sgx.static_address` was renamed to `sgx.nonpie_binary` and now has to be inserted manually by users (`sgx_sign` tools doesn't know about the binaries run inside, which can be even provided or generated in runtime by the user's workload). - Caveat: the memory gap for non-PIE executables was removed because it requires adding a new option to the manifest to be cleanly implemented. This is left for some future loader rework PR.
Python example
This directory contains an example for running Python 3 in Graphene, including the Makefile and a template for generating the manifest. The application is tested on Ubuntu 16.04 and Ubuntu 18.04, with both normal Linux and SGX platforms. The tested versions of Python are 3.5 and 3.6.
Generating the manifest
Installing prerequisites
For generating the manifest and running the test scripts, please run the following command to install the required utility packages (Ubuntu-specific):
sudo apt-get install libnss-mdns
Building for Linux
Run make (non-debug) or make DEBUG=1 (debug) in the directory.
Building for SGX
Run make SGX=1 (non-debug) or make SGX=1 DEBUG=1 (debug) in the directory.
Building with a local Python installation
By default, the make command creates the manifest for the Python binary from
the system installation. If you have a local installation, you may create the
manifest with the PYTHONPATH variable set accordingly. You can also specify
a particular version of Python. For example:
make PYTHONPATH=<python install path> PYTHONVERSION=python3.6 SGX=1
By default, PYTHONPATH=/usr and PYTHONVERSION=python3.5.
Run Python with Graphene
Here's an example of running Python scripts under Graphene:
Without SGX:
./pal_loader ./python scripts/helloworld.py
./pal_loader ./python scripts/fibonacci.py
With SGX:
SGX=1 ./pal_loader ./python scripts/helloworld.py
SGX=1 ./pal_loader ./python scripts/fibonacci.py
You can also manually run included tests:
SGX=1 ./run-tests.sh