Supporting these options complicates the design of Graphene and loading
logic significantly, providing little useful functionality:
- loader.exec:
- the main user of it were our tests
- worked only for the first process spawned inside Graphene, as it
was a unidirectional manifest->binary mapping, so the child
process didn't know about the corresponding manifest.
- sgx.sigfile:
- probably all existing usages of it were completely redundant
- was resolved relatively to CWD instead of the executable location,
which made it mostly useless
From now on, the correct location of the files is:
- either place the manifest and sigfile next to the binary, with a
matching name, or
- create a symlink to the binary in the folder where manifests are
stored and launch it through this symlink
R example
This directory contains an example for running R in Graphene, including the Makefile and a template for generating the manifest. The application was tested on Ubuntu 16.04, with both normal Linux and SGX platforms.
This example is temporarily broken until we rewrite Graphene loader
Generating the manifest
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 R installation
By default, the make command creates the manifest for the system R binary
(/usr/lib/R/bin/exec/R). If you have a local R installation, you may create
the manifest with the R_HOME variable set accordingly. For example:
make R_HOME=<install path>/lib/R SGX=1
Run R with Graphene
When running R with Graphene, please use the --vanilla or --no-save option.
Here's an example of running an R script under Graphene:
Without SGX:
./pal_loader R.manifest --slave --vanilla -f scripts/sample.r
./pal_loader R.manifest --slave --vanilla -f scripts/R-benchmark-25.R
With SGX:
SGX=1 ./pal_loader R.manifest --slave --vanilla -f scripts/sample.r
SGX=1 ./pal_loader R.manifest --slave --vanilla -f scripts/R-benchmark-25.R