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.
2.3 KiB
Apache
This directory contains the Makefile and the template manifest for the most recent version of Apache web server (as of this writing, version 2.4.41). This was tested on a machine with SGX v1 and Ubuntu 16.04.
The Makefile and the template manifest contain extensive comments. Please review them to understand the requirements for Apache running under Graphene-SGX.
We build Apache from the source code instead of using an existing installation. On Ubuntu 16.04, please make sure that the following packages are installed:
sudo apt-get install -y build-essential flex libapr1-dev libaprutil1-dev libpcre2-dev \
apache2-utils libssl-dev
Quick Start
# build Apache and the final manifest
make SGX=1
# run original Apache against HTTP and HTTPS benchmarks (benchmark-http.sh, uses ab)
make start-native-server &
../common_tools/benchmark-http.sh 127.0.0.1:8001
../common_tools/benchmark-http.sh https://127.0.0.1:8443
kill -SIGINT %%
# run Apache in non-SGX Graphene against HTTP and HTTPS benchmarks
make start-graphene-server &
../common_tools/benchmark-http.sh 127.0.0.1:8001
../common_tools/benchmark-http.sh https://127.0.0.1:8443
kill -SIGINT %%
# run Apache in Graphene-SGX against HTTP and HTTPS benchmarks
SGX=1 make start-graphene-server &
../common_tools/benchmark-http.sh 127.0.0.1:8001
../common_tools/benchmark-http.sh https://127.0.0.1:8443
kill -SIGINT %%
# you can also test the server using other utilities like wget
wget http://127.0.0.1:8001/random/10K.1.html
wget https://127.0.0.1:8443/random/10K.1.html
Running Apache with Different MPMs
The Apache server can run with several different multi-processing modules (MPMs). The two popular ones are Prefork and Worker MPMs. The Prefork MPM uses multiple child processes with one thread each, and each process handles one connection at a time. The Worker MPM uses multiple child processes with many threads each, and each thread handles one connection at a time.
The supplied Makefile allows to run Apache in both configurations:
make start-native-server # run with Prefork MPM
make start-graphene-server # run with Prefork MPM
make start-native-multithreaded-server # run with Worker MPM
make start-graphene-multithreaded-server # run with Worker MPM