This is a major refactor of the way manifests are loaded and handled, which will be followed by a complete rework of the loader code (which will include e.g. centralized config). Changes/fixes: - Huge part of manifest handling was refactored and untangled. - Starting without a manifest is now disallowed. This was actually accidentally broken for some time and no one complained. It also makes little sense in practice and in Graphene's overall design, e.g. it conflicts with protected argv. - Now we only allow starting by giving the executable, not manifest (the magic resolution logic was removed). - Now manifests are sent over pipes between parent and children, instead of children finding and loading them on their own. This is a preparation for the upcoming centralized manifests change. - Previously manifests were parsed 2 times on Linux and 3 times on Linux-SGX (by untrusted PAL, trusted PAL and LibOS). This is now fixed. - The common `pal_main()` now requires that the backend-specific PAL loader loads the manifest before calling it. SGX code already has to do it (for proper initialization), so let's unify this interface for all PALs. - Fix for a PAL crash when manifest size was divisible by page size (sic!). NULL termination was missing, but most of the time the padding to page size saved Graphene from crashing.
1.6 KiB
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