Files
Michał Kowalczyk e587869e13 [LibOS+Pal] manifest: Remove support for loader.exec and sgx.sigfile
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
2020-10-23 00:06:46 +02:00
..

Curl

This directory contains a Makefile and template manifest to run curl on Graphene. We tested it with curl 7.47.0 on Ubuntu 16.04 and with curl 7.58.0 on Ubuntu 18.04. This example uses curl installed on the system instead of compiling from source as some of the other examples do. On Ubuntu 16.04, please make sure that libnss-mdns is installed and if not, run the following command:

sudo apt-get install libnss-mdns

The Makefile and the template manifest contain comments to hopefully make them easier to understand.

Quick Start

To run the regression test execute make check. To do the same for SGX, execute make SGX=1 check. The regression test downloads the index page of example.com, thus it requires Internet connection.